This is an automated email from the ASF dual-hosted git repository.

gilbert pushed a commit to branch 1.6.x
in repository https://gitbox.apache.org/repos/asf/mesos.git

commit da82ef99dee540b1ea165599b74a3b8bc497f1fe
Author: Andrei Budnik <[email protected]>
AuthorDate: Mon Feb 11 12:51:31 2019 -0800

    Fixed `ROOT_PidNamespace` test after enabling launcher sealing.
    
    Previously, this test accessed `comm` file of `init` process to
    find out the name of the containerizer launcher binary. After we
    introduced launcher sealing, this file does not represent binary
    name anymore, so we are accessing `cmdline` file instead.
    
    Review: https://reviews.apache.org/r/69951/
    (cherry picked from commit b0b5e3d89542ce2b958953326ab6b94f718d134e)
---
 src/tests/containerizer/isolator_tests.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/tests/containerizer/isolator_tests.cpp 
b/src/tests/containerizer/isolator_tests.cpp
index bdc3619..0f82516 100644
--- a/src/tests/containerizer/isolator_tests.cpp
+++ b/src/tests/containerizer/isolator_tests.cpp
@@ -120,7 +120,7 @@ TEST_F(NamespacesIsolatorTest, ROOT_PidNamespace)
 
   // Write the command's pid namespace inode and init name to files.
   const string command =
-    "stat -Lc %i /proc/self/ns/pid > ns && (cat /proc/1/comm > init)";
+    "stat -Lc %i /proc/self/ns/pid > ns && (cat /proc/1/cmdline > init)";
 
   process::Future<Containerizer::LaunchResult> launch =
     containerizer.get()->launch(

Reply via email to