[
https://issues.apache.org/jira/browse/MESOS-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joris Van Remoortere updated MESOS-3475:
----------------------------------------
Description:
Currently the {{TestContainerizer}} modifies the environment variables. Since
these are global variables, this can cause other threads reading these
variables to get inconsistent results, or even segfault if they happen to read
while the environment is being changed.
Synchronizing within the TestContainerizer is not sufficient. We should pass
the environment variables into a fork, or set them on the command line of an
execute.
was:
Currently the `TestContainerizer` modifies the environment variables. Since
these are global variables, this can cause other threads reading these
variables to get inconsistent results, or even segfault if they happen to read
while the environment is being changed.
Synchronizing within the TestContainerizer is not sufficient. We should pass
the environment variables into a fork, or set them on the command line of an
execute.
> TestContainerizer should not modify global environment variables
> ----------------------------------------------------------------
>
> Key: MESOS-3475
> URL: https://issues.apache.org/jira/browse/MESOS-3475
> Project: Mesos
> Issue Type: Bug
> Reporter: Joris Van Remoortere
>
> Currently the {{TestContainerizer}} modifies the environment variables. Since
> these are global variables, this can cause other threads reading these
> variables to get inconsistent results, or even segfault if they happen to
> read while the environment is being changed.
> Synchronizing within the TestContainerizer is not sufficient. We should pass
> the environment variables into a fork, or set them on the command line of an
> execute.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
