When we execute XHarness commands, we must do so using the launchctl command which spawns the process in a different user session. The env variables are not forwarded and they are lost.
Since the runtime mono tests rely on these, we must make them available in the payload scripts (send them as options and export them again).
When we execute XHarness commands, we must do so using the
launchctlcommand which spawns the process in a different user session. The env variables are not forwarded and they are lost.Since the runtime mono tests rely on these, we must make them available in the payload scripts (send them as options and export them again).