November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-987) It take lot of time to start some jenkins slaves

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-987?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-987: ------------------------------------- https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-utils/commit/12bf01... https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-utils/commit/47b692... > It take lot of time to start some jenkins slaves > ------------------------------------------------ > > Key: SWSQE-987 > URL: https://issues.jboss.org/browse/SWSQE-987 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > Noticed that it takes lot of time to start e.g. jenkins-slave-kiali-build because it is installing and downloading some stuff before it's registered with jenkins. > We need to check our docker slaves and update them not to do that. Either create already prepared docker image or do installation steps after it's registered with jenkins. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-987) It take lot of time to start some jenkins slaves

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-987?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-987: ------------------------------------- Also removed automatic installation of JDK where it's not necessary > It take lot of time to start some jenkins slaves > ------------------------------------------------ > > Key: SWSQE-987 > URL: https://issues.jboss.org/browse/SWSQE-987 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > Noticed that it takes lot of time to start e.g. jenkins-slave-kiali-build because it is installing and downloading some stuff before it's registered with jenkins. > We need to check our docker slaves and update them not to do that. Either create already prepared docker image or do installation steps after it's registered with jenkins. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-987) It take lot of time to start some jenkins slaves

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-987?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-987. --------------------------------- Resolution: Done > It take lot of time to start some jenkins slaves > ------------------------------------------------ > > Key: SWSQE-987 > URL: https://issues.jboss.org/browse/SWSQE-987 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > Noticed that it takes lot of time to start e.g. jenkins-slave-kiali-build because it is installing and downloading some stuff before it's registered with jenkins. > We need to check our docker slaves and update them not to do that. Either create already prepared docker image or do installation steps after it's registered with jenkins. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4772) [DMN Editor] Open Properties panel by default

by Lubomír Terifaj (Jira)

[ https://issues.jboss.org/browse/DROOLS-4772?page=com.atlassian.jira.plugi... ] Lubomír Terifaj updated DROOLS-4772: ------------------------------------ Description: To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. h4. Acceptance criteria After DMN editor is opened, Properties panel is opened immediately without any interaction required. It is possible to close and open it back using "Properties panel button". was:To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. > [DMN Editor] Open Properties panel by default > --------------------------------------------- > > Key: DROOLS-4772 > URL: https://issues.jboss.org/browse/DROOLS-4772 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: Lubomír Terifaj > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. > h4. Acceptance criteria > After DMN editor is opened, Properties panel is opened immediately without any interaction required. > It is possible to close and open it back using "Properties panel button". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4772) [DMN Editor] Open Properties panel by default

by Lubomír Terifaj (Jira)

[ https://issues.jboss.org/browse/DROOLS-4772?page=com.atlassian.jira.plugi... ] Lubomír Terifaj commented on DROOLS-4772: ----------------------------------------- Hi [~manstis], [~jomarko], if the issue is not reasonable to you, feel free to close it. Thank you! > [DMN Editor] Open Properties panel by default > --------------------------------------------- > > Key: DROOLS-4772 > URL: https://issues.jboss.org/browse/DROOLS-4772 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: Lubomír Terifaj > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4772) [DMN Editor] Open diagram editor by default

by Lubomír Terifaj (Jira)

[ https://issues.jboss.org/browse/DROOLS-4772?page=com.atlassian.jira.plugi... ] Lubomír Terifaj updated DROOLS-4772: ------------------------------------ Description: To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. (was: Open diagram editor by default) > [DMN Editor] Open diagram editor by default > ------------------------------------------- > > Key: DROOLS-4772 > URL: https://issues.jboss.org/browse/DROOLS-4772 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: Lubomír Terifaj > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4772) [DMN Editor] Open Properties panel by default

by Lubomír Terifaj (Jira)

[ https://issues.jboss.org/browse/DROOLS-4772?page=com.atlassian.jira.plugi... ] Lubomír Terifaj updated DROOLS-4772: ------------------------------------ Summary: [DMN Editor] Open Properties panel by default (was: [DMN Editor] Open diagram editor by default) > [DMN Editor] Open Properties panel by default > --------------------------------------------- > > Key: DROOLS-4772 > URL: https://issues.jboss.org/browse/DROOLS-4772 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: Lubomír Terifaj > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4772) [DMN Editor] Open diagram editor by default

by Lubomír Terifaj (Jira)

Lubomír Terifaj created DROOLS-4772: --------------------------------------- Summary: [DMN Editor] Open diagram editor by default Key: DROOLS-4772 URL: https://issues.jboss.org/browse/DROOLS-4772 Project: Drools Issue Type: Task Components: DMN Editor Affects Versions: 7.29.0.Final Reporter: Lubomír Terifaj Assignee: Michael Anstis Open diagram editor by default -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4449) Visual design enhancements: Scenario/DMN error overlays

by Brian Dellascio (Jira)

[ https://issues.jboss.org/browse/DROOLS-4449?page=com.atlassian.jira.plugi... ] Brian Dellascio edited comment on DROOLS-4449 at 11/15/19 11:53 AM: -------------------------------------------------------------------- Hi [~tirelli], I was under the assumption they all were, but the last two were the newest additions to the stack based on our brief meeting a couple of weeks back. I also realized this morning that I hadn't uploaded the updates to the first mockup on Marvel. I've done that and it's up-to-date now. Apologies for the confusion it may have caused. CC [~uxdlc] was (Author: bdellasc): Hi [~tirelli], I was under the assumption they all were, but the last two were the newest additions to the stack. I also realized this morning that I hadn't uploaded the updates to the first mockup. I've done that and it's up-to-date now. Apologies for the confusion. CC [~uxdlc] > Visual design enhancements: Scenario/DMN error overlays > ------------------------------------------------------- > > Key: DROOLS-4449 > URL: https://issues.jboss.org/browse/DROOLS-4449 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor, Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Brian Dellascio > Priority: Major > Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools > Attachments: ban-solid.svg, check-circle-regular.svg, check-circle-solid.svg, exclamation-circle-regular.svg, exclamation-circle-solid.svg > > > Scenario and DMN editors share design solutions for displaying errors in graphs (models) and grids (scenario test, dmn boxed expressions.) Support design consistency where applicable, while also documenting unique solutions per context. > Verification conditions: > - Review interaction design wireframes and click-thrus to offer recommendations for a consistent presentation for error overlays for the two editors (Scenario and DMN) > - Wireframes posted at: https://issues.jboss.org/browse/DROOLS-4257 and https://issues.jboss.org/browse/DROOLS-3953. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-12718: ------------------------------------- [~tommaso-borgato] OK - we found the problem. This issue is with this condition: https://github.com/wildfly/wildfly/blob/18.0.1.Final/clustering/web/cache... This skips triggering a mutation of the object in the event that the old value and new value reference the same object. However, the QE test application uses setAttribute(...) to force replication of an @Immutable object. > Clustering: replicated-cache sampling errors > -------------------------------------------- > > Key: WFLY-12718 > URL: https://issues.jboss.org/browse/WFLY-12718 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Tommasso Borgato > Assignee: Paul Ferraro > Priority: Blocker > > The issue is about replicated-cache in fail-over tests. > WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script: > {noformat} > embed-server --server-config=standalone-ha.xml > /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add() > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add() > /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl) > {noformat} > The test is run with wildfly-18.0.0.Final.zip; > The same tests run with version wildfly-17.0.1.Final.zip do not have any problem; > hence this looks like a regression; > As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error; > Here are the runs that exhibit this issue: > - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.r...] > We also repeated the tests to make sure it can be reproduced: > - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.r...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 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 November 2019