[JBoss JIRA] (WFCORE-3875) [jdk10] PatchModuleInvalidationWithRenamingFailureTestCase#test failure
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3875?page=com.atlassian.jira.plugi... ]
Richard Opalka updated WFCORE-3875:
-----------------------------------
Fix Version/s: 6.0.0.Alpha5
> [jdk10] PatchModuleInvalidationWithRenamingFailureTestCase#test failure
> -----------------------------------------------------------------------
>
> Key: WFCORE-3875
> URL: https://issues.jboss.org/browse/WFCORE-3875
> Project: WildFly Core
> Issue Type: Bug
> Components: Patching , Test Suite
> Affects Versions: 5.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Richard Opalka
> Labels: Java11
> Fix For: 6.0.0.Alpha5
>
>
> org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase#test from patching module of wildfly-core fails with JDK10, works fine with JDK9.
>
> *reproduce*
> {noformat}
> wildfly-core]$ mvn test -Dtest=PatchModuleInvalidationWithRenamingFailureTestCase#test -pl patching
> ...
> [INFO] Running org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.363 s <<< FAILURE! - in org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase
> [ERROR] test(org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase) Time elapsed: 0.359 s <<< FAILURE!
> java.lang.AssertionError:
> Expected: is <false>
> but: was <true>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.junit.Assert.assertThat(Assert.java:923)
> at org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase.test(PatchModuleInvalidationWithRenamingFailureTestCase.java:97)
> ...
> {noformat}
>
> Environment:
> {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 10.0.1, vendor: Oracle Corporation
> {noformat}
> Byteman is being involved in the test.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFCORE-3874) [jdk10] FileSystemDeploymentServiceUnitTestCase#testNoUndeployment failure
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3874?page=com.atlassian.jira.plugi... ]
Richard Opalka reassigned WFCORE-3874:
--------------------------------------
Assignee: Richard Opalka (was: ehsavoie Hugonnet)
> [jdk10] FileSystemDeploymentServiceUnitTestCase#testNoUndeployment failure
> --------------------------------------------------------------------------
>
> Key: WFCORE-3874
> URL: https://issues.jboss.org/browse/WFCORE-3874
> Project: WildFly Core
> Issue Type: Bug
> Components: Deployment Scanner, Test Suite
> Affects Versions: 5.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Richard Opalka
> Labels: Java11
>
> org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase#testNoUndeployment from deployment-scanner module of wildfly-core fails with JDK10, works fine with JDK9.
> *reproduce*
> {noformat}
> wildfly-core]$ mvn test -Dtest=FileSystemDeploymentServiceUnitTestCase#testNoUndeployment -pl deployment-scanner
> ...
> [INFO] Running org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.121 s <<< FAILURE! - in org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase
> [ERROR] testNoUndeployment(org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase) Time elapsed: 0.115 s <<< FAILURE!
> java.lang.AssertionError: RuntimeException expected
> at org.junit.Assert.fail(Assert.java:88)
> at org.jboss.as.server.deployment.scanner.FileSystemDeploymentServiceUnitTestCase.testNoUndeployment(FileSystemDeploymentServiceUnitTestCase.java:1798)
> ...
> {noformat}
> Environment:
> {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 10.0.1, vendor: Oracle Corporation
> {noformat}
> Byteman is being involved in the test.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFCORE-3875) [jdk10] PatchModuleInvalidationWithRenamingFailureTestCase#test failure
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3875?page=com.atlassian.jira.plugi... ]
Richard Opalka reassigned WFCORE-3875:
--------------------------------------
Assignee: Richard Opalka (was: Alexey Loubyansky)
> [jdk10] PatchModuleInvalidationWithRenamingFailureTestCase#test failure
> -----------------------------------------------------------------------
>
> Key: WFCORE-3875
> URL: https://issues.jboss.org/browse/WFCORE-3875
> Project: WildFly Core
> Issue Type: Bug
> Components: Patching , Test Suite
> Affects Versions: 5.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Richard Opalka
> Labels: Java11
>
> org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase#test from patching module of wildfly-core fails with JDK10, works fine with JDK9.
>
> *reproduce*
> {noformat}
> wildfly-core]$ mvn test -Dtest=PatchModuleInvalidationWithRenamingFailureTestCase#test -pl patching
> ...
> [INFO] Running org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.363 s <<< FAILURE! - in org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase
> [ERROR] test(org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase) Time elapsed: 0.359 s <<< FAILURE!
> java.lang.AssertionError:
> Expected: is <false>
> but: was <true>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.junit.Assert.assertThat(Assert.java:923)
> at org.jboss.as.patching.tests.PatchModuleInvalidationWithRenamingFailureTestCase.test(PatchModuleInvalidationWithRenamingFailureTestCase.java:97)
> ...
> {noformat}
>
> Environment:
> {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 10.0.1, vendor: Oracle Corporation
> {noformat}
> Byteman is being involved in the test.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFCORE-3869) [jdk10] DeletionCollisionTest#testFileLockByRemoveContent failure
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3869?page=com.atlassian.jira.plugi... ]
Richard Opalka reassigned WFCORE-3869:
--------------------------------------
Assignee: Richard Opalka (was: ehsavoie Hugonnet)
> [jdk10] DeletionCollisionTest#testFileLockByRemoveContent failure
> -----------------------------------------------------------------
>
> Key: WFCORE-3869
> URL: https://issues.jboss.org/browse/WFCORE-3869
> Project: WildFly Core
> Issue Type: Bug
> Components: Deployment Scanner, Test Suite
> Affects Versions: 5.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Richard Opalka
> Labels: Java11
>
> org.jboss.as.repository.DeletionCollisionTest#testFileLockByRemoveContent from deployment-repository module of wildfly-core fails with JDK10, works fine with JDK9.
>
> *reproduce*
> {noformat}
> wildfly-core]$ mvn test -Dtest=DeletionCollisionTest#testFileLockByRemoveContent -pl deployment-repository
> ...
> [INFO] Running org.jboss.as.repository.DeletionCollisionTest
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.307 s <<< FAILURE! - in org.jboss.as.repository.DeletionCollisionTest
> [ERROR] testFileLockByRemoveContent(org.jboss.as.repository.DeletionCollisionTest) Time elapsed: 0.301 s <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.as.repository.DeletionCollisionTest.testFileLockByRemoveContent(DeletionCollisionTest.java:117)
> ...
> {noformat}
>
> Exception expected by the test - [WFLYDR0019|https://github.com/wildfly/wildfly-core/blob/master/deployment...]
> {noformat}
> Caused by: org.jboss.as.repository.ExplodedContentException: WFLYDR0019: Deployment is locked by another operation
> at org.jboss.as.repository.ContentRepositoryImpl.readContent(ContentRepositoryImpl.java:550)
> at org.jboss.as.repository.DeletionCollisionTest.lambda$testFileLockByRemoveContent$3(DeletionCollisionTest.java:111)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
>
> Actual exception thrown with JDK10
> {noformat}
> Caused by: org.jboss.as.repository.ExplodedContentException: WFLYDR0020: Error accessing deployment files
> at org.jboss.as.repository.ContentRepositoryImpl.readContent(ContentRepositoryImpl.java:563)
> at org.jboss.as.repository.DeletionCollisionTest.lambda$testFileLockByRemoveContent$3(DeletionCollisionTest.java:111)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: java.io.FileNotFoundException: target
> at org.jboss.as.repository.PathUtil.getFile(PathUtil.java:376)
> at org.jboss.as.repository.PathUtil.getFile(PathUtil.java:374)
> at org.jboss.as.repository.PathUtil.getFile(PathUtil.java:374)
> at org.jboss.as.repository.PathUtil.getFile(PathUtil.java:374)
> at org.jboss.as.repository.PathUtil.getFile(PathUtil.java:374)
> at org.jboss.as.repository.PathUtil.getFile(PathUtil.java:374)
> at org.jboss.as.repository.PathUtil.readFile(PathUtil.java:356)
> at org.jboss.as.repository.ContentRepositoryImpl.readContent(ContentRepositoryImpl.java:554)
> ... 5 more
> {noformat}
> Environment:
> {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 10.0.1, vendor: Oracle Corporation
> {noformat}
> Byteman is being involved in the test.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2787:
-------------------------------------
[~karreiro][~manstis][~tirelli]
Another iteration, using a list for the dialog that allows users to Manage the data types (add, remove, edit). One of the big differences here is that the user adds a "generic" data type first, then defines it inline in the list. So in the simplest of cases there will be 2 dropdowns: the first to select the type [Simple] and the second to select the value [String, Number, Boolean...]
Please note: Theses are quick Balsamiq mockups - I just did a quick pass, to get feedback before I go too far down this direction. I added annotations to explain my ideas. I have a feeling I'm missing something in this one, but not sure. Let me know, thanks.
* Inline edit example:
!Manage1.png|thumbnail!
* Add example:
* !Manage2.png|thumbnail!
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2738.bmpr, Manage1.png, Manage2.png, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2787:
--------------------------------
Attachment: Manage1.png
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2738.bmpr, Manage1.png, Manage2.png, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2787:
--------------------------------
Attachment: Manage2.png
> "Data Type" tree-grid table interactions.
> -----------------------------------------
>
> Key: DROOLS-2787
> URL: https://issues.jboss.org/browse/DROOLS-2787
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2738.bmpr, Manage1.png, Manage2.png, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.)
> * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.)
> * *Remove* Data Types from the list of available selections.
> * be prevented from making selections that are not valid or would cause an error.
> * know that when I edit a data type the changes will be updated in the DMN model.
> Functional considerations/ pre conditions:
> * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-2823) FEEL Parser: `not` breaks with `list contains`
by Edoardo Vacchi (JIRA)
Edoardo Vacchi created DROOLS-2823:
--------------------------------------
Summary: FEEL Parser: `not` breaks with `list contains`
Key: DROOLS-2823
URL: https://issues.jboss.org/browse/DROOLS-2823
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Edoardo Vacchi
Assignee: Edson Tirelli
*list contains([1,2,3,4,5,6], 3)* returns true
*not(list contains([1,2,3,4,5,6], 3))* returns “list contains([1,2,3,4,5,6], 3)”, it should return false
Most likely related to an issue with the parse tree branches
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months