Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Mesosphere Sprint 2018-21, Mesosphere Sprint 2018-22
-
8
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.
Attachments
Issue Links
- breaks
-
MESOS-2407 libprocess segfaults when using GLOG_v=2
- Resolved
-
MESOS-6985 os::getenv() can segfault
- Resolved
-
MESOS-8134 SlaveTest.ContainersEndpoint is flaky due to getenv crash.
- Resolved
-
MESOS-8875 `leveldb::PosixEnv::DeleteFile()` can segfault.
- Resolved