June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-283) Istio/Kiali Checker Running After Calling Job Completes

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-283?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-283: ------------------------------------ Completed. Delete job Kiali-on-Openshift-SWSQE-283/ > Istio/Kiali Checker Running After Calling Job Completes > ------------------------------------------------------- > > Key: SWSQE-283 > URL: https://issues.jboss.org/browse/SWSQE-283 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Minor > > Kiali-on-Openshift is calling Kiali-Istio-Checker as a Post-Build step, but because this step is asynchronous Kiali-on-Openshift completes at times before Kiali-Istio-Checker job starts. > Make Kiali-Istio-Checker a build step, and not a post-build step. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2619) Tests are not executed due to test name not following required pattern

by Barbora Siskova (JIRA)

Barbora Siskova created DROOLS-2619: --------------------------------------- Summary: Tests are not executed due to test name not following required pattern Key: DROOLS-2619 URL: https://issues.jboss.org/browse/DROOLS-2619 Project: Drools Issue Type: Bug Reporter: Barbora Siskova Assignee: Barbora Siskova There are multiple tests in some of our repositories (namely drools, droolsjbpm-integration, kie-wb-common and appformer repositories) with names not following the default wildcard patterns of maven-surefire-plugin and maven-failsafe-plugin. As a result, these tests are not executed on Jenkins. Proper names for test classes should follow these patterns: - **/Test*.java, **/*Test.java, **/*TestCase.java for surefire plugin or - **/IT*.java, **/*IT.java, **/*ITCase.java for failsafe plugin; -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-283) Istio/Kiali Checker Running After Calling Job Completes

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-283?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-283: ------------------------------------ New job w/ fix: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi... > Istio/Kiali Checker Running After Calling Job Completes > ------------------------------------------------------- > > Key: SWSQE-283 > URL: https://issues.jboss.org/browse/SWSQE-283 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Minor > > Kiali-on-Openshift is calling Kiali-Istio-Checker as a Post-Build step, but because this step is asynchronous Kiali-on-Openshift completes at times before Kiali-Istio-Checker job starts. > Make Kiali-Istio-Checker a build step, and not a post-build step. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-283) Istio/Kiali Checker Running After Calling Job Completes

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-283: ---------------------------------- Summary: Istio/Kiali Checker Running After Calling Job Completes Key: SWSQE-283 URL: https://issues.jboss.org/browse/SWSQE-283 Project: Kiali QE Issue Type: Bug Reporter: Matt Mahoney Assignee: Matt Mahoney Priority: Minor Kiali-on-Openshift is calling Kiali-Istio-Checker as a Post-Build step, but because this step is asynchronous Kiali-on-Openshift completes at times before Kiali-Istio-Checker job starts. Make Kiali-Istio-Checker a build step, and not a post-build step. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-282) modify "assert_all_items" to create more user defined combinations

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-282?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-282. ----------------------------------- Resolution: Done PR merged. > modify "assert_all_items" to create more user defined combinations > ------------------------------------------------------------------ > > Key: SWSQE-282 > URL: https://issues.jboss.org/browse/SWSQE-282 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > modify "assert_all_items" to create more user-defined combinations -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-218) Istio/Kiali Checker Running After Calling Job Completes

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-218?page=com.atlassian.jira.pl... ] Matt Mahoney deleted HAWKULARQE-218: ------------------------------------ > Istio/Kiali Checker Running After Calling Job Completes > ------------------------------------------------------- > > Key: HAWKULARQE-218 > URL: https://issues.jboss.org/browse/HAWKULARQE-218 > Project: Hawkular QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Minor > > Kiali-on-Openshift is calling Kiali-Istio-Checker as a Post-Build step, but because this step is asynchronous Kiali-on-Openshift completes at times before Kiali-Istio-Checker job starts. > Make Kiali-Istio-Checker a build step, and not a post-build step. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-218) Istio/Kiali Checker Running After Calling Job Completes

by Matt Mahoney (JIRA)

Matt Mahoney created HAWKULARQE-218: --------------------------------------- Summary: Istio/Kiali Checker Running After Calling Job Completes Key: HAWKULARQE-218 URL: https://issues.jboss.org/browse/HAWKULARQE-218 Project: Hawkular QE Issue Type: Bug Reporter: Matt Mahoney Assignee: Matt Mahoney Priority: Minor Kiali-on-Openshift is calling Kiali-Istio-Checker as a Post-Build step, but because this step is asynchronous Kiali-on-Openshift completes at times before Kiali-Istio-Checker job starts. Make Kiali-Istio-Checker a build step, and not a post-build step. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2549) [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2549?page=com.atlassian.jira.plugi... ] Michael Anstis reopened DROOLS-2549: ------------------------------------ > [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase > ------------------------------------------------------------------- > > Key: DROOLS-2549 > URL: https://issues.jboss.org/browse/DROOLS-2549 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Fix For: 7.8.0.Final > > > {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes. > At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}). > Changes required for this JIRA (split into sub-tasks when work starts):- > * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller > * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children > * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/) > * When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}} (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3904) NPE at TAB completion

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3904?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3904: ---------------------------------------------- Even by handling the NPE at the CLI level, we then run into AESH-471 in this case. > NPE at TAB completion > --------------------- > > Key: WFCORE-3904 > URL: https://issues.jboss.org/browse/WFCORE-3904 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 5.0.0.Final > Reporter: Erich Duda > Assignee: Jean-Francois Denise > Priority: Blocker > Labels: blocker-WF14 > > When you write some command into the CLI prompt (without enter), move cursor to beginning of line and hit TAB, the CLI crashes on {{NullPointerException}}. > {code} > [standalone@localhost:9990 /] /system-property=x:read-resource > read-resource read-resource-description Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.NullPointerException > at org.jboss.as.cli.impl.aesh.cmd.operation.OperationCommandContainer.isOperation(OperationCommandContainer.java:53) > at org.jboss.as.cli.impl.aesh.CLICommandRegistry.getCommand(CLICommandRegistry.java:258) > at org.jboss.as.cli.impl.aesh.CLICommandRegistry.isLegacyCommand(CLICommandRegistry.java:343) > at org.jboss.as.cli.impl.aesh.CLICompletionHandler.complete(CLICompletionHandler.java:134) > at org.jboss.as.cli.impl.CLICommandCompleter.doComplete(CLICommandCompleter.java:132) > at org.jboss.as.cli.impl.CLICommandCompleter.complete(CLICommandCompleter.java:54) > at org.jboss.as.cli.impl.aesh.CLICompletionHandler.complete(CLICompletionHandler.java:69) > at org.jboss.as.cli.impl.aesh.CLICompletionHandler.complete(CLICompletionHandler.java:45) > at org.aesh.readline.completion.CompletionHandler.createCompletionList(CompletionHandler.java:134) > at org.aesh.readline.completion.CompletionHandler.complete(CompletionHandler.java:102) > at org.aesh.readline.action.mappings.Complete.accept(Complete.java:62) > at org.aesh.readline.Readline$AeshInputProcessor.parse(Readline.java:245) > at org.aesh.readline.Readline$AeshInputProcessor.access$100(Readline.java:174) > at org.aesh.readline.Readline.readInput(Readline.java:95) > at org.aesh.readline.Readline.access$1000(Readline.java:57) > at org.aesh.readline.Readline$AeshInputProcessor.lambda$start$1(Readline.java:333) > at org.aesh.terminal.EventDecoder.accept(EventDecoder.java:118) > at org.aesh.terminal.EventDecoder.accept(EventDecoder.java:31) > at org.aesh.io.Decoder.write(Decoder.java:133) > at org.aesh.readline.tty.terminal.TerminalConnection.openBlocking(TerminalConnection.java:212) > at org.aesh.readline.tty.terminal.TerminalConnection.openBlocking(TerminalConnection.java:199) > at org.jboss.as.cli.impl.ReadlineConsole$CLITerminalConnection.lambda$null$1(ReadlineConsole.java:171) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3909) jboss-cli script does not delegate -D properties to java process

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3909?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3909: ---------------------------------------------- [~eduda], the picture seems a bit more complex. CLI launcher does propagate the system properties (by direct calls to setProperty), but it does that after logging has been initialised. As you suggest, It should be handled at the script level. > jboss-cli script does not delegate -D properties to java process > ---------------------------------------------------------------- > > Key: WFCORE-3909 > URL: https://issues.jboss.org/browse/WFCORE-3909 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Scripts > Affects Versions: 5.0.0.Final > Reporter: Erich Duda > Assignee: Jean-Francois Denise > > *Scenario:* I want to change logging configuration of CLI using system properties. My expectation is that I just put the properties on command line as arguments. > {code} > ./jboss-cli.sh -Dlogging.configuration=... -Djboss.cli.log.level=TRACE -Djboss.cli.log.level=TRACE > {code} > However what I actually have to do is to put the properties into the {{JAVA_OPTS}} env variable. > {code} > JAVA_OPTS="-Dlogging.configuration=... -Djboss.cli.log.level=TRACE -Djboss.cli.log.level=TRACE" ./jboss-cli.sh > {code} > This is different behavior than I am used to standalone.sh script. IMO it is more natural to put the properties as arguments of the script. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 June 2018