----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69532/#review211126 -----------------------------------------------------------
FAIL: Some of the unit tests failed. Please check the relevant logs. Reviews applied: `['69532']` Failed command: `Start-MesosCITesting` All the build artifacts available at: http://dcos-win.westus2.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/2684/mesos-review-69532 Relevant logs: - [mesos-tests.log](http://dcos-win.westus2.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/2684/mesos-review-69532/logs/mesos-tests.log): ``` W1208 02:01:13.988322 17180 slave.cpp:3922] Ignoring shutdown framework 2fac819f-38bc-4374-bafc-b53e1e3e93b3-0000 because it is terminating I1208 02:01:13.990461 14116 master.cpp:1275] Agent 2fac819f-38bc-4374-bafc-b53e1e3e93b3-S0 at slave(461)@192.10.1.6:52872 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net) disconnected I1208 02:01:13.990461 14116 master.cpp:3278] Disconnecting agent 2fac819f-38bc-4374-bafc-b53e1e3e93b3-S0 at slave(461)@192.10.1.6:52872 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net) I1208 02:01:13.990461 14116 master.cpp:3297] Deactivating agent 2fac819f-38bc-4374-bafc-b53e1e3e93b3-S0 at slave(461)@192.10.1.6:52872 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net) I1208 02:01:13.991320 15556 hierarchical.cpp:357] Removed framework 2fac819f-38bc-4374-bafc-b53e1e3e93b3-0000 I1208 02:01:13.991320 15556 hierarchical.cpp:801] Agent 2fac819f-38bc-4374-bafc-b53e1e3e93b3-S0 deactivated I1208 02:01:13.992337 15556 containerizer.cpp:2463] Destroying container 39b3ca99-2040-46ff-bc62-b5dde5cd84b7 in RUNNING state I1208 02:01:13.992337 15556 containerizer.cpp:3130] Transitioning the state of container 39b3ca99-2040-46ff-bc62-b5dde5cd84b7 from RUNNING to DESTROYING I1208 02:01:13.993332 15556 launcher.cpp:161] Asked to destroy container 39b3ca99-2040-46ff-bc62-b5dde5cd84b7 W1208 02:01:13.994343 1652[ OK ] IsolationFlag/MemoryIsolatorTest.ROOT_MemUsage/0 (688 ms) [----------] 1 test from IsolationFlag/MemoryIsolatorTest (706 ms total) [----------] Global test environment tear-down [==========] 1057 tests from 104 test cases ran. (531578 ms total) [ PASSED ] 1056 tests. [ FAILED ] 1 test, listed below: [ FAILED ] DockerFetcherPluginTest.INTERNET_CURL_FetchImage 1 FAILED TEST YOU HAVE 231 DISABLED TESTS 0 process.cpp:1423] Failed to recv on socket WindowsFD::Type::SOCKET=2168 to peer '192.10.1.6:54687': IO failed with error code: The specified network name is no longer available. W1208 02:01:13.994343 16520 process.cpp:838] Failed to recv on socket WindowsFD::Type::SOCKET=1756 to peer '192.10.1.6:54688': IO failed with error code: The specified network name is no longer available. I1208 02:01:14.079972 18040 containerizer.cpp:2969] Container 39b3ca99-2040-46ff-bc62-b5dde5cd84b7 has exited I1208 02:01:14.109994 18184 master.cpp:1117] Master terminating I1208 02:01:14.110961 14116 hierarchical.cpp:643] Removed agent 2fac819f-38bc-4374-bafc-b53e1e3e93b3-S0 I1208 02:01:14.434022 16520 process.cpp:927] Stopped the socket accept loop ``` - Mesos Reviewbot Windows On Dec. 8, 2018, 1:55 a.m., Jie Yu wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69532/ > ----------------------------------------------------------- > > (Updated Dec. 8, 2018, 1:55 a.m.) > > > Review request for mesos, Andrei Budnik and James Peach. > > > Bugs: MESOS-9462 > https://issues.apache.org/jira/browse/MESOS-9462 > > > Repository: mesos > > > Description > ------- > > Make sure that container's runtime dir has device file access. Some > Linux distributions will mount `/run` with `nodev`, restricting > accessing to device files under `/run`. However, Mesos prepares device > files for containers under container's runtime dir (which is typically > under `/run`) and bind mount into container root filesystems. Therefore, > we need to make sure those device files can be accessed by the > container. We need to do a self bind mount and remount with proper > options if necessary. See MESOS-9462 for more details. > > > Diffs > ----- > > src/linux/fs.hpp 04bd706447ec7edf6b1f05fb416c834d189b2218 > src/linux/fs.cpp 6ff8b4dd8ac69f4afd5fa24bb38eb26753e6bcdd > src/slave/containerizer/mesos/isolators/filesystem/linux.cpp > c318fb956e22f07f32fd18b238b86f6a1ee0b2bf > src/slave/containerizer/mesos/isolators/volume/host_path.cpp > 2e4cd2b9b852b0c95a2957f4bed33fe54f093e3d > src/slave/containerizer/mesos/launch.cpp > 6aa4397aa0fc9e1c93a0f3a13fbe0a55c5a02f0c > > > Diff: https://reviews.apache.org/r/69532/diff/2/ > > > Testing > ------- > > sudo make check > > > Thanks, > > Jie Yu > >
