[jboss-jira] [JBoss JIRA] (WFLY-12899) Failing JMXPropertyEditorsTestCase in 18.0.0.Final

[Bartosz Baranowski (Jira)]

    [ https://issues.redhat.com/browse/WFLY-12899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948903#comment-13948903 ] 

Bartosz Baranowski edited comment on WFLY-12899 at 1/15/20 5:17 AM:
--------------------------------------------------------------------

Test is designed to check env variables expansion.  So naturally one env var that is present in any OS( one way or another) has been chosen. Since different OS store it a bit differently test has to do some digging and store name of env variable in USER_SYS_PROP.

Problem with docker is that it does great job at isolating running process  that is - unless you set explicitly some env variable it wont be there, even though it is present in OS/env. (Im assuming that jenkins triggers docker to test WFLY).

One solution would be to add -e switch to docker(or any kind of equivalent), second to ignore this part of test if no env value can  be detected.

[~james-crowley-ibm] - can you please try -e ?


was (Author: baranowb):
Test is designed to check env variables expansion.  So naturally one env var that is present in any OS( one way or another) has been chosen. Since different OS store it a bit differently test has to do some digging and stores name of env variable in USER_SYS_PROP.

Problem with docker is that it does great job at isolating running process  that is - unless you set explicitly some env variable it wont be there, even though it is present in OS/env. (Im assuming that jenkins triggers docker to test WFLY).

One solution would be to add -e switch to docker(or any kind of equivalent), second to ignore this part of test if no env value can  be detected.

[~james-crowley-ibm] - can you please try -e ?

> Failing JMXPropertyEditorsTestCase in 18.0.0.Final
> --------------------------------------------------
>
>                 Key: WFLY-12899
>                 URL: https://issues.redhat.com/browse/WFLY-12899
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 18.0.0.Final
>            Reporter: James Crowley
>            Assignee: Bartosz Baranowski
>            Priority: Major
>
> When calling "./mvnw install -DallTests", it gets up to the JMXPropertyEditorsTestCase and fails with this error, "Caused by: java.lang.IllegalStateException: Failed to resolve expression: env.USER"}}}}". 
> Looking at the source code for the test [here|https://github.com/wildfly/wildfly/blob/1bf993be72b570a0c780a58ba05cabafe1ce7935/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/ee/jmx/property/JMXPropertyEditorsTestCase.java#L148], it looks like USER is suppose to be defined by USER_SYS_PROP. 
> I am not sure what the problem is but I know it is failing somewhere in the above test.
> You can see the full log in the in Adopt's test  [here|https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/1436/consoleText].



--
This message was sent by Atlassian Jira
(v7.13.8#713008)