[ https://issues.redhat.com/browse/WFLY-12899?page=com.atlassian.jira.plugi... ] 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 ? -- This message was sent by Atlassian Jira (v7.13.8#713008)