----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68354/#review207460 -----------------------------------------------------------
FAIL: Some of the unit tests failed. Please check the relevant logs. Reviews applied: `['68354']` Failed command: `Start-MesosCITesting` All the build artifacts available at: http://dcos-win.westus.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/2178/mesos-review-68354 Relevant logs: - [mesos-tests.log](http://dcos-win.westus.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/2178/mesos-review-68354/logs/mesos-tests.log): ``` os/signal.signal_recv(0x0) /usr/local/go/src/runtime/sigqueue.go:139 +0xad os/signal.loop() /usr/local/go/src/os/signal/signal_ d:\dcos\mesos\mesos\3rdparty\libprocess\include\process\gmock.hpp(247): ERROR: this mock object (used in test ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.TaskRunning/0) should be deleted but never is. Its address is @0000028465AD1098. d:\dcos\mesos\mesos\src\tests\mock_registrar.cpp(54): ERROR: this mock object (used in test ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.TaskRunning/0) should be deleted but never is. Its address is @0000028469464590. d:\dcos\mesos\mesos\src\tests\default_executor_tests.cpp(126): ERROR: this mock object (used in test ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.TaskRunning/0) should be deleted but never is. Its address is @000002846B519040. ERROR: 3 leaked mock objects found at program exit. unix.go:22 +0x29 created by os/signal.init.0 /usr/local/go/src/os/signal/signal_unix.go:28 +0x48 ' If recovery failed due to a change in configuration and you want to keep the current agent id, you might want to change the `--reconfiguration_policy` flag to a more permissive value. To restart this agent with a new agent id instead, do as follows: rm -f C:\Users\jenkins\AppData\Local\Temp\HZkNks\meta\slaves\latest This ensures that the agent does not recover old live executors. If you use the Docker containerizer and think that the Docker daemon state is broken, you can try to clear it. But be careful: these commands will erase all containers and images from this host, not just those started by Mesos! docker kill $(docker ps -q) docker rm $(docker ps -a -q) docker rmi $(docker images -q) Finally, restart the agent. ``` - Mesos Reviewbot Windows On Aug. 17, 2018, 1:54 a.m., Meng Zhu wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68354/ > ----------------------------------------------------------- > > (Updated Aug. 17, 2018, 1:54 a.m.) > > > Review request for mesos, Benjamin Mahler and Gastón Kleiman. > > > Repository: mesos > > > Description > ------- > > This test verifies that the agent backs-off properly when > retrying authentication according to the configured parameters. > > Also mocked `Slave::authenticate()` for this test. > > > Diffs > ----- > > src/slave/slave.hpp 0420109ac93e1249906c52437e5859c5ee033fb6 > src/tests/authentication_tests.cpp f7a2cf17cf6154c9c67e405661bba57cf1254845 > src/tests/mock_slave.hpp 9a74bf35d2cab0a72ba6376392239d8080a49304 > src/tests/mock_slave.cpp 94a5b0d20475f49dde99108a009682b520175aa4 > > > Diff: https://reviews.apache.org/r/68354/diff/5/ > > > Testing > ------- > > make check > > Added test continuously running without failure. > > > Thanks, > > Meng Zhu > >
