February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3103) Support run test at project level

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3103?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3103: ---------------------------------- Sprint: 2019 Week 02-04, 2019 Week 08-10 (was: 2019 Week 02-04) > Support run test at project level > --------------------------------- > > Key: DROOLS-3103 > URL: https://issues.jboss.org/browse/DROOLS-3103 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Toni Rikkola > Priority: Major > > As user I want to be able to run all the scenarios in my project from project view -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3592) Undo/Redo regression on right panel

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3592?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3592: ---------------------------------- Sprint: 2019 Week 08-10 > Undo/Redo regression on right panel > ----------------------------------- > > Key: DROOLS-3592 > URL: https://issues.jboss.org/browse/DROOLS-3592 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > After naming/renaming of header, undo/redo does not restore correctly the right panel status. > Start this ticket after merging of DROOLS-3242, DROOLS-3357, DROOLS-3466, DROOLS-3485, DROOLS-3568 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3341) Duplicate DO columns

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3341?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3341: ---------------------------------- Sprint: 2019 Week 08-10 > Duplicate DO columns > -------------------- > > Key: DROOLS-3341 > URL: https://issues.jboss.org/browse/DROOLS-3341 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > Attachments: duplicate.png, multiDO.png > > > As a user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. scenario with more than one instance of “Person”...), so that I can create a test scenario. > * As a user I want a means to create a data object instance in the test template using an existing statement column, so that I can quickly create instances from the test table. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2808) [Guided Decision Table] Dependent enums are not loaded

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2808?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-2808. ------------------------------- Resolution: Done Closing as: - Not a customer jira - Our focus is now on DMN and ScenarioSimulation running on standalone lightweight workbench > [Guided Decision Table] Dependent enums are not loaded > ------------------------------------------------------ > > Key: DROOLS-2808 > URL: https://issues.jboss.org/browse/DROOLS-2808 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: Car.java, Screenshot from 2018-07-31 12-00-11.png, prices.enumeration > > > The guided decision table doesn't load dependent enums. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2680) Run a single row scenario test

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-2680?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-2680: ---------------------------------- Sprint: 2019 Week 08-10 > Run a single row scenario test > ------------------------------ > > Key: DROOLS-2680 > URL: https://issues.jboss.org/browse/DROOLS-2680 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > Priority: Minor > > As a business analyst I want to run a single row scenario test so that I can run only one test when I have too many rows in the scenario test. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1860) Verification reporting: Merge same messages in analysis report into one line

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1860?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1860. ------------------------------- Resolution: Rejected Won't be implemented due to changing our focus to new DMN and ScenarionSimulation designers running standalone on new lightweight business central. > Verification reporting: Merge same messages in analysis report into one line > ---------------------------------------------------------------------------- > > Key: DROOLS-1860 > URL: https://issues.jboss.org/browse/DROOLS-1860 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta5 > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools, verifier > > To keep the analysis report readable as much as possible, merge all messages with the same meaning and content (differ only in the row number) into single row in the analysis report panel. Currently are merged only "Empty Rules", "Missing Condition" and "Missing Action". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11745) The layers testsuite should use thin servers

by Jean-Francois Denise (Jira)

Jean-Francois Denise created WFLY-11745: ------------------------------------------- Summary: The layers testsuite should use thin servers Key: WFLY-11745 URL: https://issues.jboss.org/browse/WFLY-11745 Project: WildFly Issue Type: Enhancement Components: Test Suite Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise The layers testsuite is provisioning a bunch of different servers. It should use thin servers (i.e. jars in the maven repo, not in the modules dirs) as it's not validating anything that differs between a thin and fat server. This will reduce the disk io and peak FS space requirements on the CI servers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4339) The layers testsuite should use thin servers

by Jean-Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFCORE-4339?page=com.atlassian.jira.plugi... ] Jean-Francois Denise moved WFLY-11745 to WFCORE-4339: ----------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4339 (was: WFLY-11745) Component/s: Test Suite (was: Test Suite) > The layers testsuite should use thin servers > -------------------------------------------- > > Key: WFCORE-4339 > URL: https://issues.jboss.org/browse/WFCORE-4339 > Project: WildFly Core > Issue Type: Enhancement > Components: Test Suite > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Priority: Major > > The layers testsuite is provisioning a bunch of different servers. It should use thin servers (i.e. jars in the maven repo, not in the modules dirs) as it's not validating anything that differs between a thin and fat server. This will reduce the disk io and peak FS space requirements on the CI servers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11213) On release of batch it still contained JDBC statements logged

by Daniel Wehrle (Jira)

[ https://issues.jboss.org/browse/WFLY-11213?page=com.atlassian.jira.plugin... ] Daniel Wehrle commented on WFLY-11213: -------------------------------------- Hi [~smarlow], will this bug be fixed in final release of WF16? Or: will WF16 include Hibernate 5.3.8? In the beta of WF16 it is 5.3.7? > On release of batch it still contained JDBC statements logged > ------------------------------------------------------------- > > Key: WFLY-11213 > URL: https://issues.jboss.org/browse/WFLY-11213 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 14.0.1.Final > Environment: Java 8_181 > Wildfly 14.0.1.Final > Reporter: Cody Lerum > Assignee: Scott Marlow > Priority: Major > > After updating from Wildfly 11 (Hibernate 5.1.10) to Wildfly 14.0.1 (Hibernate 5.3.6) I've started seeing the following log messages > I’m starting to see the log message > {code:java} > 2018-10-17 20:12:47,571 INFO [org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl] (default task-54) HHH000010: On release of batch it still contained JDBC statements > 2018-10-17 20:12:47,572 ERROR [org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl] (default task-54) HHH000352: Unable to release batch statement... > {code} > I’ve debugged where that is getting logged and all I can find is a single statement at the time. > insert into EventLog (entityId, entityType, ipAddress, message, time, user, id) values (?, ?, ?, ?, ?, ?, ?) > The only insert that is being created is actually being persisted to the database so this may be a spurious message. > From my early debugging this appears to happen when 1 entity is persisted which does not need an immediate inset (due to having a generated pk) and then in another method of the same transaction an entity is persisted that does need an immediate insert because of a auto increment pk. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-594) Jenkins Jobs Hung

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-594?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-594. --------------------------------- Resolution: Done Fix was introduced in kubernetes-1.14.5. The plugin was updated to this version. > Jenkins Jobs Hung > ----------------- > > Key: SWSQE-594 > URL: https://issues.jboss.org/browse/SWSQE-594 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Filip Brychta > Priority: Major > Attachments: image-2019-02-11-16-35-41-783.png > > > Jenkins jobs hung in the following state: > !image-2019-02-11-16-35-41-783.png|thumbnail! > After nearly 30 min, restarting the Jenkins service cleared the issue and the jobs ran fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 February 2019