-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: None
-
Component/s: client-libs
-
None
-
master
We had many false positive reports of failed JCK tests due to missing environment variables. By default, the JCK suite only whitelists a few variables.
Previously we had to specify those variables manually with "-env:", but this isn't suitable for mach5, as there are some variables that are new for every session, like XAUTHORITY.
So JCK-7322838 introduced javatest.processCommand.inheritEnv system property.
Now we need to update mach5 client headful job files to use JCK_LAUNCHER_OPTIONS=-Djavatest.processCommand.inheritEnv=true
Previously we had to specify those variables manually with "-env:", but this isn't suitable for mach5, as there are some variables that are new for every session, like XAUTHORITY.
So JCK-7322838 introduced javatest.processCommand.inheritEnv system property.
Now we need to update mach5 client headful job files to use JCK_LAUNCHER_OPTIONS=-Djavatest.processCommand.inheritEnv=true