----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69532/#review211133 -----------------------------------------------------------
FAIL: Some of the unit tests failed. Please check the relevant logs. Reviews applied: `['69537', '69532']` Failed command: `Start-MesosCITesting` All the build artifacts available at: http://dcos-win.westus2.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/2685/mesos-review-69532 Relevant logs: - [mesos-tests.log](http://dcos-win.westus2.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/2685/mesos-review-69532/logs/mesos-tests.log): ``` W1210 04:32:00.422715 16520 slave.cpp:3922] Ignoring shutdown framework 696485c1-2184-4ebc-9cbc-6a89fd4336eb-0000 because it is terminating I1210 04:32:00.424713 17776 master.cpp:1275] Agent 696485c1-2184-4ebc-9cbc-6a89fd4336eb-S0 at slave(461)@192.10.1.6:57186 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net) disconnected I1210 04:32:00.424713 17776 master.cpp:3278] Disconnecting agent 696485c1-2184-4ebc-9cbc-6a89fd4336eb-S0 at slave(461)@192.10.1.6:57186 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net) I1210 04:32:00.424713 17776 master.cpp:3297] Deactivating agent 696485c1-2184-4ebc-9cbc-6a89fd4336eb-S0 at slave(461)@192.10.1.6:57186 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net) I1210 04:32:00.425709 14436 hierarchical.cpp:357] Removed framework 696485c1-2184-4ebc-9cbc-6a89fd4336eb-0000 I1210 04:32:00.425709 14436 hierarchical.cpp:801] Agent 696485c1-2184-4ebc-9cbc-6a89fd4336eb-S0 deactivated I1210 04:32:00.426745 13868 containerizer.cpp:2463] Destroying container 1f074ecd-dc20-4492-b59b-7b740b85e795 in RUNNING state I1210 04:32:00.426745 13868 containerizer.cpp:3130] Transitioning the state of container 1f074ecd-dc20-4492-b59b-7b740b85e795 from RUNNING to DESTROYING I1210 04:32:00.427716 13868 launcher.cpp:161] Asked to destroy container 1f074ecd-dc20-4492-b59b-7b740b85e795 W1210 04:32:00.428705 12320 process.cpp:838] Failed to recv on socket WindowsFD::Type::SOCKET=3968 to peer '192.10.1.6:58999': IO failed with error code: The specified network name is no longer available. W1210 04:32:00.428705 12320 process.cpp:1423] Failed to recv on socket WindowsFD::Type::SOCKET=2560 to peer '192.10.1.6:58998': IO failed with error code: The specified network name is no longer available. I1210 04:32:00.489790 17492 containerizer.cpp:2969] Container 1f074ecd-dc20-4492-b59b-7b740b85e795 has exited I1210 04:32:00.517755 18116 master.cpp:1117] Master terminating I1210 04:32:00.518723 13868 hierarchical.cpp:643] Removed agent 696485c1-2184-4ebc[ OK ] IsolationFlag/MemoryIsolatorTest.ROOT_MemUsage/0 (680 ms) [----------] 1 test from IsolationFlag/MemoryIsolatorTest (699 ms total) [----------] Global test environment tear-down [==========] 1057 tests from 104 test cases ran. (536620 ms total) [ PASSED ] 1056 tests. [ FAILED ] 1 test, listed below: [ FAILED ] DockerFetcherPluginTest.INTERNET_CURL_InvokeFetchByName 1 FAILED TEST YOU HAVE 231 DISABLED TESTS -9cbc-6a89fd4336eb-S0 I1210 04:32:00.839767 12320 process.cpp:927] Stopped the socket accept loop ``` - Mesos Reviewbot Windows On Dec. 10, 2018, 2:16 p.m., Jie Yu wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69532/ > ----------------------------------------------------------- > > (Updated Dec. 10, 2018, 2:16 p.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/3/ > > > Testing > ------- > > sudo make check > > Built a new Mesos Mini image and tested. The workload runs fine. The same > workload fails on `mesos/mesos-mini-2018-12-06` > ``` > docker run --rm --privileged -p 5050:5050 -p 5051:5051 -p 8080:8080 > jieyu/mesos-mini > ``` > > ```json > { > "id": "/test", > "cmd": "dd if=/dev/zero of=file bs=1024 count=1 oflag=dsync", > "cpus": 1, > "mem": 128, > "disk": 128, > "instances": 1, > "container": { > "type": "MESOS", > "docker": { > "image": "ubuntu:18.04" > } > } > } > ``` > > > Thanks, > > Jie Yu > >
