[ https://issues.apache.org/jira/browse/MESOS-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15635760#comment-15635760 ]
haosdent commented on MESOS-6541: --------------------------------- We didn't run test cases after {{clone()}} for now and only Linux support this. To make all test cases run an isolated environment, we have used docker in Apache Jenkins CI. I still prefer the current way to make test cases run without {{CLONE_NEWNS}}, it would expose the problem more obviously if Mesos has leak mounts. > Mesos test should mount cgroups_root > ------------------------------------ > > Key: MESOS-6541 > URL: https://issues.apache.org/jira/browse/MESOS-6541 > Project: Mesos > Issue Type: Bug > Components: cgroups, test > Reporter: Yan Xu > > Currently on hosts without prior cgroups setup and sysfs is mounted at /sys, > mesos tests would fail like this: > {noformat:title=} > [ RUN ] HTTPCommandExecutorTest.TerminateWithACK > F1103 19:54:40.807538 439804 command_executor_tests.cpp:236] > CHECK_SOME(_containerizer): Failed to create launcher: Failed to create Linux > launcher: Failed to mount cgroups hierarchy at '/sys/fs/cgroup/fr > eezer': Failed to create directory '/sys/fs/cgroup/freezer': No such file or > directory > {noformat} > This is because the agent chooses to use {{LinuxLauncher}} based on > availability of the {{freezer}} subsystem alone. However for it to work, one > needs to do the following > {noformat:title=} > mount -t tmpfs cgroup_root /sys/fs/cgroup > {noformat} > in order to make {{/sys/fs/cgroup}} writable. > I have always run the command manually in the past when this failure happens > but this could be baffling especially to new developers. Mesos tests should > just mount it if it's not already done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)