----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69892/#review212542 -----------------------------------------------------------
FAIL: Some of the unit tests failed. Please check the relevant logs. Reviews applied: `['69858', '69866', '69892']` Failed command: `Start-MesosCITesting` All the build artifacts available at: http://dcos-win.westus2.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/2850/mesos-review-69892 Relevant logs: - [mesos-tests.log](http://dcos-win.westus2.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/2850/mesos-review-69892/logs/mesos-tests.log): ``` I0205 08:43:13.151952 32844 master.cpp:11317] Removing task 83482d1a-9498-4eb7-af15-05073d895a62 with resources cpus(allocated: *):4; mem(allocated: *):2048; disk(allocated: *):1024; ports(allocated: *):[31000-32000] of framework 9bfba4c6-997f-4c2e-bff6-5867256f8ba7-0000 on agent 9bfba4c6-997f-4c2e-bff6-5867256f8ba7-S0 at slave(477)@192.10.1.6:59972 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net) I0205 08:43:13.153949 33920 master.cpp:1269] Agent 9bfba4c6-997f-4c2e-bff6-5867256f8ba7-S0 at slave(477)@192.10.1.6:59972 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net) disconnected I0205 08:43:13.154947 33920 master.cpp:3272] Disconnecting agent 9bfba4c6-997f-4c2e-bff6-5867256f8ba7-S0 at slave(477)@192.10.1.6:59972 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net) I0205 08:43:13.154947 33920 master.cpp:3291] Deactivating agent 9bfba4c6-997f-4c2e-bff6-5867256f8ba7-S0 at slave(477)@192.10.1.6:59972 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net) I0205 08:43:13.154947 25360 hierarchical.cpp:358] Removed framework 9bfba4c6-997f-4c2e-bff6-5867256f8ba7-0000 I0205 08:43:13.154947 25360 hierarchical.cpp:793] Agent 9bfba4c6-997f-4c2e-bff6-5867256f8ba7-S0 deactivated I0205 08:43:13.155947 34176 containerizer.cpp:2477] Destroying container 7995f0b2-2fba-430c-98a1-abd316d3485a in RUNNING state I0205 08:43:13.155947 34176 containerizer.cpp:3144] Transitioning the state of container 7995f0b2-2fba-430c-98a1-abd316d3485a from RUNNING to DESTROYING I0205 08:43:13.156953 3417[ OK ] IsolationFlag/MemoryIsolatorTest.ROOT_MemUsage/0 (687 ms) [----------] 1 test from IsolationFlag/MemoryIsolatorTest (704 ms total) [----------] Global test environment tear-down [==========] 1095 tests from 104 test cases ran. (506130 ms total) [ PASSED ] 1094 tests. [ FAILED ] 1 test, listed below: [ FAILED ] DockerFetcherPluginTest.INTERNET_CURL_InvokeFetchByName 1 FAILED TEST YOU HAVE 231 DISABLED TESTS 6 launcher.cpp:161] Asked to destroy container 7995f0b2-2fba-430c-98a1-abd316d3485a W0205 08:43:13.157941 30808 process.cpp:1423] Failed to recv on socket WindowsFD::Type::SOCKET=3456 to peer '192.10.1.6:61876': IO failed with error code: The specified network name is no longer available. W0205 08:43:13.157941 30808 process.cpp:838] Failed to recv on socket WindowsFD::Type::SOCKET=3512 to peer '192.10.1.6:61877': IO failed with error code: The specified network name is no longer available. I0205 08:43:13.255445 33920 containerizer.cpp:2983] Container 7995f0b2-2fba-430c-98a1-abd316d3485a has exited I0205 08:43:13.283437 34472 master.cpp:1109] Master terminating I0205 08:43:13.285444 30556 hierarchical.cpp:644] Removed agent 9bfba4c6-997f-4c2e-bff6-5867256f8ba7-S0 I0205 08:43:13.722429 30808 process.cpp:927] Stopped the socket accept loop ``` - Mesos Reviewbot Windows On Feb. 5, 2019, 7:40 a.m., Chun-Hung Hsiao wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69892/ > ----------------------------------------------------------- > > (Updated Feb. 5, 2019, 7:40 a.m.) > > > Review request for mesos, Benjamin Bannier, James DeFelice, and Jie Yu. > > > Bugs: MESOS-9544 > https://issues.apache.org/jira/browse/MESOS-9544 > > > Repository: mesos > > > Description > ------- > > If a CSI volume has been node-published before a reboot, SLRP will now > try to bring it back to node-published again. This is important to > perform synchronous persistent volume cleanup for `DESTROY`. > > To achieve this, in addition to keeping track of the boot ID when a CSI > volume is node-staged in `VolumeState.vol_ready_boot_id` (formerly > `VolumeState.boot_id`), SLRP now also keeps track of the boot ID when > the volume is node-published. This helps SLRP to better determine if a > volume has been published before reboot. > > > Diffs > ----- > > src/csi/state.proto 264a5657dd37605a6f3bdadd0e8d18ba9673191a > src/resource_provider/storage/provider.cpp > d6e20a549ede189c757ae3ae922ab7cb86d2be2c > src/tests/storage_local_resource_provider_tests.cpp > e8ed20f818ed7f1a3ce15758ea3c366520443377 > > > Diff: https://reviews.apache.org/r/69892/diff/1/ > > > Testing > ------- > > `make check` > > Testing for publish failures will be done later in chain. > > > Thanks, > > Chun-Hung Hsiao > >
