July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4555) Randomly fail an add operation on subsystem remoting

by Vratislav Marek (Jira)

Vratislav Marek created WFCORE-4555: --------------------------------------- Summary: Randomly fail an add operation on subsystem remoting Key: WFCORE-4555 URL: https://issues.jboss.org/browse/WFCORE-4555 Project: WildFly Core Issue Type: Bug Components: Remoting Environment: * Any java * RHEL6 & RHEL7 Reporter: Vratislav Marek Assignee: Flavia Rainone Operation add on subsystem remoting randomly fail with the message:: {code} { "outcome" => "failed", "failure-description" => "WFLYCTL0441: Operation has resulted in failed or missing services WFLYCTL0448: 1 additional services are down due to their dependencies being missing or failed", "rolled-back" => true } {code} Used operation: {code} { "operation" => "add", "address" => [("subsystem" => "remoting")], "worker" => "default-remoting", "send-buffer-size" => 1, "receive-buffer-size" => 1, "buffer-region-size" => 1, "transmit-window-size" => 1, "receive-window-size" => 1, "max-outbound-channels" => 1, "max-inbound-channels" => 1, "authorize-id" => "abc", "auth-realm" => "abc", "authentication-retries" => 1, "max-outbound-messages" => 1, "max-inbound-messages" => 1, "heartbeat-interval" => 1, "max-inbound-message-size" => 1L, "max-outbound-message-size" => 1L, "server-name" => "abc", "sasl-protocol" => "abc", "worker-read-threads" => undefined, "worker-task-core-threads" => undefined, "worker-task-keepalive" => undefined, "worker-task-limit" => undefined, "worker-task-max-threads" => undefined, "worker-write-threads" => undefined } {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-4161: -------------------------------------- [~danielezonca], I think this can be a part of the *Settings* panel. Now, you can set the DMN model there. It should be very easy to add a new *Decision Service* option. > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12244) MaximumTimeoutTestCase fails a lot

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/WFLY-12244?page=com.atlassian.jira.plugin... ] Thomas Jenkinson reassigned WFLY-12244: --------------------------------------- Assignee: Ondrej Chaloupka (was: Michael Musgrove) > MaximumTimeoutTestCase fails a lot > ---------------------------------- > > Key: WFLY-12244 > URL: https://issues.jboss.org/browse/WFLY-12244 > Project: WildFly > Issue Type: Bug > Components: Test Suite, Transactions > Reporter: Kabir Khan > Assignee: Ondrej Chaloupka > Priority: Critical > > This is failing a lot on CI for loads of pull requests: https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... > It also happens on master JDK 11 https://ci.wildfly.org/viewLog.html?buildId=156368&buildTypeId=WF_MasterW... > CC [~tomjenkinson] [~ochaloup] [~zhfeng] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4162) Scenario Test: UX for background data

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4162?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4162: --------------------------------------- [~zhutaojiajia] Sorry but I don't think you are covering the requirement entirely. - How is the user supposed to specify multiple instances? - How specify the mapping? Let me recap the steps: - user creates a new test scenario - user wants to specify some data to be used in every scenario - user needs to defined the mapping for each object - user can specify multiple instances for each object Here is an example: User wants to create multiple scenarios and each of them begin with the same set of data i.e. 4 available people. In the current implementation he needs to create 4 instances (one for each person) and specify the same values for each row but he would like to do it only once. Background concept should allow him to do this mapping and define the data only once and this will be applied to each scenario as additional GIVEN data. > Scenario Test: UX for background data > ------------------------------------- > > Key: DROOLS-4162 > URL: https://issues.jboss.org/browse/DROOLS-4162 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: design1.png, design2.png, design3.png > > > As user I want to be able to specify a set of data shared by all the scenarios inside a simulation. All the data will be not editable. > Please refer to Cucumber background feature for details https://cucumber.io/docs/gherkin/reference/#background -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3953) DMN UX - error highlight in boxed expression.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3953: -------------------------------------- Sprint: 2019 Week 26-28 > DMN UX - error highlight in boxed expression. > --------------------------------------------- > > Key: DROOLS-3953 > URL: https://issues.jboss.org/browse/DROOLS-3953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ux-decision button.png, ux-decision table.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4274) Remove reference usage from xml

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4274: ---------------------------------------- Summary: Remove reference usage from xml Key: DROOLS-4274 URL: https://issues.jboss.org/browse/DROOLS-4274 Project: Drools Issue Type: Sub-task Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Remove usage of reference from xsd and xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4161) Scenario Test: UX for DMN Decision service

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4161?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4161: --------------------------------------- [~zhutaojiajia] I think it is not the most common task. It should be most common to test the entire model. [~tirelli] do you agree? And about the demo: what about update change the decision service to test after file creation? Do you suggest not to support this feature? > Scenario Test: UX for DMN Decision service > ------------------------------------------ > > Key: DROOLS-4161 > URL: https://issues.jboss.org/browse/DROOLS-4161 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to test my decision service from a DMN model. > User needs to specify DMN model and decision service name to be tested. > Note: a decision service contains only a subset of decisions so the template (header) need to be updated/recreated or the information needs to be available during template creation -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4269) kogito-codegen-tests: alternative testing strategy for codegen

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4269?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4269: ----------------------------------- Story Points: 5 > kogito-codegen-tests: alternative testing strategy for codegen > -------------------------------------------------------------- > > Key: DROOLS-4269 > URL: https://issues.jboss.org/browse/DROOLS-4269 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, kogito, submarine > > Currently we are doing dynamic compilation and classloading to test code generation. I am proposing an alternative strategy that use the plain Maven plugin. > - create `kogito-codegen-tests` > - write data/rules/process sources under src/main/{java,resources} > - write tests under src/test/ > tests are now allowed to refer directly to codegenerated classes by name. > just use mvn compile test to run the tests > caveat: not sure if the maven plugin is picked up from the current source tree or from the SNAPSHOT on the nexus, we need to check this -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4256) Make Quarkus extension hot reload to also work with new rules

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4256?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4256: ----------------------------------- Story Points: 5 > Make Quarkus extension hot reload to also work with new rules > ------------------------------------------------------------- > > Key: DROOLS-4256 > URL: https://issues.jboss.org/browse/DROOLS-4256 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Edoardo Vacchi > Priority: Major > > At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-692) UI Automation - Add Breadcrumb checks

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-692?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-692: -------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/180 > UI Automation - Add Breadcrumb checks > ------------------------------------- > > Key: SWSQE-692 > URL: https://issues.jboss.org/browse/SWSQE-692 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Add checks of Breadcrumb in List and Details pages of all objects. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 July 2019