October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3149) [DMN Designer] Context top level data type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3149?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3149: -------------------------------- Description: h2. Acceptance test On Edge, Chrome (/) and Firefox (/) - Steps to reproduce fixed - Opposite way, clicking row doesn't show node specific properties was: h2. Acceptance test On Edge, Chrome (/) and Firefox - Steps to reproduce fixed - Opposite way, clicking row doesn't show node specific properties > [DMN Designer] Context top level data type > ------------------------------------------ > > Key: DROOLS-3149 > URL: https://issues.jboss.org/browse/DROOLS-3149 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: DROOLS-3149.png > > > h2. Acceptance test > On Edge, Chrome (/) and Firefox (/) > - Steps to reproduce fixed > - Opposite way, clicking row doesn't show node specific properties -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3149) [DMN Designer] Context top level data type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3149?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3149: -------------------------------- Description: h2. Acceptance test On Edge, Chrome (/) and Firefox - Steps to reproduce fixed - Opposite way, clicking row doesn't show node specific properties was: h2. Acceptance test On Edge, Chrome and Firefox - Steps to reproduce fixed - Opposite way, clicking row doesn't show node specific properties > [DMN Designer] Context top level data type > ------------------------------------------ > > Key: DROOLS-3149 > URL: https://issues.jboss.org/browse/DROOLS-3149 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: DROOLS-3149.png > > > h2. Acceptance test > On Edge, Chrome (/) and Firefox > - Steps to reproduce fixed > - Opposite way, clicking row doesn't show node specific properties -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3049) [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3049?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3049: ----------------------------------- Steps to Reproduce: # Create a DMN diagram # Add a Decision Node # Edit the Node, adding a Relation expression # Double click the Relation column header to launch the "Name and Data-type" popover # Click the "Manage" link to launch the "Data Type" dialog # The "Name and Data-type" popover should hide (it remains visible atm) > [DMN Designer] NameAndDataTypeEditorViewImpl needs to hide if the User navigates to the Data Type dialog > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3049 > URL: https://issues.jboss.org/browse/DROOLS-3049 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > > The {{NameAndDataTypeEditorViewImpl}} contains a link to the "Data Type Dialog". When this is clicked on the dialog is displayed and the _source_ {{Popover}} remains visible. When the User clicks on the dialog a mouse event is detected that is not _over_ the {{Popover}} and it closes. The proposal is to close the {{Popover}} if the User clicks on the link to the "Data Type Dialog". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3149) [DMN Designer] Context top level data type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3149?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3149: -------------------------------- Description: h2. Acceptance test On Edge, Chrome and Firefox - Steps to reproduce fixed - Opposite way, clicking row doesn't show node specific properties > [DMN Designer] Context top level data type > ------------------------------------------ > > Key: DROOLS-3149 > URL: https://issues.jboss.org/browse/DROOLS-3149 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: DROOLS-3149.png > > > h2. Acceptance test > On Edge, Chrome and Firefox > - Steps to reproduce fixed > - Opposite way, clicking row doesn't show node specific properties -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3117) [DMN Designer] Change of output data type refresh properties

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3117?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3117: ---------------------------------------- Thank-you [~jomarko] I will "resolve" this JIRA. > [DMN Designer] Change of output data type refresh properties > ------------------------------------------------------------- > > Key: DROOLS-3117 > URL: https://issues.jboss.org/browse/DROOLS-3117 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > If the output data type of Literal Expression is changed, the properties panel is refreshed and Literal Specific properties are not shown more. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3117) [DMN Designer] Change of output data type refresh properties

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3117?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3117: ------------------------------------- [~manstis] I tested today with master and can not reproduce the issue more, thanks. > [DMN Designer] Change of output data type refresh properties > ------------------------------------------------------------- > > Key: DROOLS-3117 > URL: https://issues.jboss.org/browse/DROOLS-3117 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > If the output data type of Literal Expression is changed, the properties panel is refreshed and Literal Specific properties are not shown more. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-450) Analyze Pipeline Execution Times

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-450?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-450. --------------------------------- Resolution: Done Added SWSQE-459 and SWSQE-460 for detailed steps to improve time execution > Analyze Pipeline Execution Times > -------------------------------- > > Key: SWSQE-450 > URL: https://issues.jboss.org/browse/SWSQE-450 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Filip Brychta > Priority: Minor > > PR Jenkins CI jobs are taking at times 30 min to complete. Are there any optimization opportunities that could improve on the pipeline execution time duration? > This is just *one* snapshot of a pipeline time breakdown, but perhaps s > 17 minutes was waiting (Spin up the Jenkins Agent) > 17 minutes running the jobs themselves > Almost 2 minutes (1.30 min) to Install Istio (Which doesn't sound too much) > 3 Minutes to Install Bookinfo > 8 minutes to Build and Deploy Kiali > 4 minutes -> to deploy kiali with Kiali Checker > 4 minutes -> to build with Yarn > 2 Minutes to run e2e-tests -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-460) Create more openshift clusters to run the main pipeline concurrently when needed

by Filip Brychta (Jira)

Filip Brychta created SWSQE-460: ----------------------------------- Summary: Create more openshift clusters to run the main pipeline concurrently when needed Key: SWSQE-460 URL: https://issues.jboss.org/browse/SWSQE-460 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Michael Foley SWSQE-450 identified a few options how to speed up PR job execution. Right now we have 3 triggers which are starting Istio-and-Kiali-on-Openshift job. First is nightly timer, kiali-core-pr-e2e-test and kiali-ui-pr-e2e-test. Istio-and-Kiali-on-Openshift job is not allowed to be run in parallel so when the job is in progress other runs have to wait. Also two PR jobs are using b12 cluster so when there is more PR jobs started at the same time it's sequential run again. We need to create more openshift clusters to be able to run more PR jobs in parallel (unless there is an option to deploy more istio/kiali versions to one openshift cluster). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11198) Session draining on stopped worker won't complete if further requests are made on balancer

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11198?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-11198: --------------------------------------- [~jkasik] How many cluster nodes did the test use? Could you make sure that a failover target was available at the time of the second request? > Session draining on stopped worker won't complete if further requests are made on balancer > ------------------------------------------------------------------------------------------ > > Key: WFLY-11198 > URL: https://issues.jboss.org/browse/WFLY-11198 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 15.0.0.Alpha1 > Reporter: Jan Kašík > Assignee: Radoslav Husar > Priority: Major > > When disabling worker with {{/subsystem=modcluster/proxy=default:stop(waittime=0)}}, the contexts are switched to {{disabled}} state. If there no further requests (on the same context which session currently times out) are made on a balancer, session correctly times out, contexts switches to {{stopped}} state and everything is OK. > However, when I run same stop operation, wait until contexts are switched into disabled state and in time in which sessions time out I make more requests on balancer, contexts will never switch to {{stopped}} state and session draining never completes. This happens intermittently (~60% of cases with 10 requests made after {{disabled}} state is in place). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-459) Speed up main pipeline (not including test parallelization)

by Filip Brychta (Jira)

Filip Brychta created SWSQE-459: ----------------------------------- Summary: Speed up main pipeline (not including test parallelization) Key: SWSQE-459 URL: https://issues.jboss.org/browse/SWSQE-459 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Michael Foley SWSQE-450 identified a few options how to speed up main pipeline: * Istio-and-Kiali-on-Openshift is not allowed to be run in parallel so it's the bottle neck right now -> run it in parallel but make sure it's not running concurrently on shared openshift cluster. * bookinfo installation takes ~6 minutes, it should be faster when done together with istio install in previous step if possible * Install Kiali takes ~9 minutes, we need to find out what is the longest part. e.g. if it's building it can be run in parallel with previous step (building does not need to wait for istio installation, only deploying has to) Note that this task is only to speed up the pipeline itself which will save a few minutes maximally. Another step will be to create multiple openshift clusters to be able run more pipelines concurrently. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018