> On May 24, 2018, 9:59 a.m., Mesos Reviewbot Windows wrote: > > FAIL: Some of the unit tests failed. Please check the relevant logs. > > > > Reviews applied: `['67285']` > > > > Failed command: `Start-MesosCITesting` > > > > All the build artifacts available at: > > http://dcos-win.westus.cloudapp.azure.com/mesos-build/review/67285 > > > > Relevant logs: > > > > - > > [mesos-tests-stdout.log](http://dcos-win.westus.cloudapp.azure.com/mesos-build/review/67285/logs/mesos-tests-stdout.log): > > > > ``` > > [ OK ] Endpoint/SlaveEndpointTest.NoAuthorizer/2 (104 ms) > > [----------] 9 tests from Endpoint/SlaveEndpointTest (997 ms total) > > > > [----------] 2 tests from ContainerizerType/DefaultContainerDNSFlagTest > > [ RUN ] ContainerizerType/DefaultContainerDNSFlagTest.ValidateFlag/0 > > [ OK ] ContainerizerType/DefaultContainerDNSFlagTest.ValidateFlag/0 > > (33 ms) > > [ RUN ] ContainerizerType/DefaultContainerDNSFlagTest.ValidateFlag/1 > > [ OK ] ContainerizerType/DefaultContainerDNSFlagTest.ValidateFlag/1 > > (36 ms) > > [----------] 2 tests from ContainerizerType/DefaultContainerDNSFlagTest (71 > > ms total) > > > > [----------] 1 test from IsolationFlag/CpuIsolatorTest > > [ RUN ] IsolationFlag/CpuIsolatorTest.ROOT_UserCpuUsage/0 > > [ OK ] IsolationFlag/CpuIsolatorTest.ROOT_UserCpuUsage/0 (690 ms) > > [----------] 1 test from IsolationFlag/CpuIsolatorTest (714 ms total) > > > > [----------] 1 test from IsolationFlag/MemoryIsolatorTest > > [ RUN ] IsolationFlag/MemoryIsolatorTest.ROOT_MemUsage/0 > > [ OK ] IsolationFlag/MemoryIsolatorTest.ROOT_MemUsage/0 (733 ms) > > [----------] 1 test from IsolationFlag/MemoryIsolatorTest (756 ms total) > > > > [----------] Global test environment tear-down > > [==========] 981 tests from 95 test cases ran. (437195 ms total) > > [ PASSED ] 980 tests. > > [ FAILED ] 1 test, listed below: > > [ FAILED ] > > DockerContainerizerHealthCheckTest.ROOT_DOCKER_DockerHealthStatusChange > > > > 1 FAILED TEST > > YOU HAVE 220 DISABLED TESTS > > > > ``` > > > > - > > [mesos-tests-stderr.log](http://dcos-win.westus.cloudapp.azure.com/mesos-build/review/67285/logs/mesos-tests-stderr.log): > > > > ``` > > I0524 16:58:45.636476 18624 exec.cpp:236] Executor registered on agent > > 63433979-6344-4f2e-a387-292b1267aa98-S0 > > I0524 16:58:45.640498 12736 executor.cpp:178] Received SUBSCRIBED event > > I0524 16:58:45.644471 12736 executor.cpp:182] Subscribed executor on > > windows-02.enofukwu14ruplxn0gs3yzmsgf.xx.internal.cloudapp.net > > I0524 16:58:45.645474 12736 executor.cpp:178] Received LAUNCH event > > I0524 16:58:45.649478 12736 executor.cpp:665] Starting task > > 3e38c67d-12fe-44f6-a749-d32af9b01b5c > > I0524 16:58:45.727474 12736 executor.cpp:485] Running > > 'D:\DCOS\mesos\src\mesos-containerizer.exe launch <POSSIBLY-SENSITIVE-DATA>' > > I0524 16:58:45.744447 12736 executor.cpp:678] Forked command at 11848 > > I0524 16:58:45.773442 11528 exec.cpp:445] Executor asked to shutdown > > I0524 16:58:45.774444 16156 executor.cpp:178] Received SHUTDOWN event > > I0524 16:58:45.774444 16156 executor.cpp:781] Shutting down > > I0524 16:58:45.774444 16156 executor.cpp:894] Sending SIGTERM to process > > tree at pid 11al.cpp:405] Deactivated framework > > 63433979-6344-4f2e-a387-292b1267aa98-0000 > > I0524 16:58:45.771445 19028 slave.cpp:3935] Shutting down framework > > 63433979-6344-4f2e-a387-292b1267aa98-0000 > > I0524 16:58:45.771445 20984 master.cpp:10843] Updating the state of task > > 3e38c67d-12fe-44f6-a749-d32af9b01b5c of framework > > 63433979-6344-4f2e-a387-292b1267aa98-0000 (latest state: TASK_KILLED, > > status update state: TASK_KILLED) > > I0524 16:58:45.772445 19028 slave.cpp:6656] Shutting down executor > > '3e38c67d-12fe-44f6-a749-d32af9b01b5c' of framework > > 63433979-6344-4f2e-a387-292b1267aa98-0000 at executor(1)@192.10.1.6:52010 > > I0524 16:58:45.773442 19028 slave.cpp:929] Agent terminating > > W0524 16:58:45.774444 19028 slave.cpp:3931] Ignoring shutdown framework > > 63433979-6344-4f2e-a387-292b1267aa98-0000 because it is terminating > > I0524 16:58:45.774444 20984 master.cpp:10942] Removing task > > 3e38c67d-12fe-44f6-a749-d32af9b01b5c with resources cpus(allocated: *):4; > > mem(allocated: *):2048; disk(allocated: *):1024; ports(allocated: > > *):[31000-32000] of framework 63433979-6344-4f2e-a387-292b1267aa98-0000 on > > agent 63433979-6344-4f2e-a387-292b1267aa98-S0 at > > slave(448)@192.10.1.6:51989 > > (windows-02.enofukwu14ruplxn0gs3yzmsgf.xx.internal.cloudapp.net) > > I0524 16:58:45.778443 20984 master.cpp:1293] Agent > > 63433979-6344-4f2e-a387-292b1267aa98-S0 at slave(448)@192.10.1.6:51989 > > (windows-02.enofukwu14ruplxn0gs3yzmsgf.xx.internal.cloudapp.net) > > disconnected > > I0524 16:58:45.778443 20984 master.cpp:3303] Disconnecting agent > > 63433979-6344-4f2e-a387-292b1267aa98-S0 at slave(448)@192.10.1.6:51989 > > (windows-02.enofukwu14ruplxn0gs3yzmsgf.xx.internal.cloudapp.net) > > I0524 16:58:45.778443 20984 master.cpp:3322] Deactivating agent > > 63433979-6344-4f2e-a387-292b1267aa98-S0 at slave(448)@192.10.1.6:51989 > > (windows-02.enofukwu14ruplxn0gs3yzmsgf.xx.internal.cloudapp.net) > > I0524 16:58:45.779451 20336 hierarchical.cpp:344] Removed framework > > 63433979-6344-4f2e-a387-292b1267aa98-0000 > > I0524 16:58:45.779451 21312 containerizer.cpp:2401] Destroying container > > 029e9ee9-403f-475d-b74b-9879517f1db3 in RUNNING state > > I0524 16:58:45.779451 20336 hierarchical.cpp:766] Agent > > 63433979-6344-4f2e-a387-292b1267aa98-S0 deactivated > > I0524 16:58:45.779451 21312 containerizer.cpp:3015] Transitioning the state > > of container 029e9ee9-403f-475d-b74b-9879517f1db3 from RUNNING to DESTROYING > > I0524 16:58:45.780485 21312 launcher.cpp:156] Asked to destroy container > > 029e9ee9-403f-475d-b74b-9879517f1db3 > > I0524 16:58:45.860872 16364 containerizer.cpp:2854] Container > > 029e9ee9-403f-475d-b74b-9879517f1db3 has exited > > I0524 16:58:45.890127 21024 master.cpp:1135] Master terminating > > I0524 16:58:45.892877 20336 hierarchical.cpp:609] Removed agent > > 63433979-6344-4f2e-a387-292b1267aa98-S0 > > I0524 16:58:46.335894 19736 process.cpp:940] Stopped the socket accept loop > > ```
You can ignore this. We're debugging... - Andrew ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67285/#review203786 ----------------------------------------------------------- On May 24, 2018, 8:48 a.m., James Peach wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67285/ > ----------------------------------------------------------- > > (Updated May 24, 2018, 8:48 a.m.) > > > Review request for mesos, Andrew Schwartzmeyer and Till Toenshoff. > > > Repository: mesos > > > Description > ------- > > The JWT test keys were only used by the JWT tests, so there was > no necessity for them to be in a header file. Moved them into the > source file to fix `make distcheck` which was failing because the > `jwt_keys.hpp` header wasn't included in the distribution. > > > Diffs > ----- > > 3rdparty/libprocess/src/tests/jwt_keys.hpp > 0fb9a989da4d0ff2eaf6b304922ae68206319079 > 3rdparty/libprocess/src/tests/jwt_tests.cpp > 581438d7b8811474d694e9482dfffe8b5068e53f > > > Diff: https://reviews.apache.org/r/67285/diff/1/ > > > Testing > ------- > > make check (Fedora 27) > > > Thanks, > > James Peach > >
