mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mesos Reviewbot Windows <revi...@mesos.apache.org>
Subject Re: Review Request 66178: Added a test to verify that task launch order is enforced.
Date Tue, 20 Mar 2018 21:56:54 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/66178/#review199591
-----------------------------------------------------------



FAIL: Some of the unit tests failed. Please check the relevant logs.

Reviews applied: `['66118', '66119', '66120', '65679', '66126', '66143', '66144', '66145',
'66178']`

Failed command: `Start-MesosCITesting`

All the build artifacts available at: http://dcos-win.westus.cloudapp.azure.com/mesos-build/review/66178

Relevant logs:

- [mesos-tests-stdout.log](http://dcos-win.westus.cloudapp.azure.com/mesos-build/review/66178/logs/mesos-tests-stdout.log):

```
[       OK ] Endpoint/SlaveEndpointTest.NoAuthorizer/2 (109 ms)
[----------] 9 tests from Endpoint/SlaveEndpointTest (1043 ms total)

[----------] 2 tests from ContainerizerType/DefaultContainerDNSFlagTest
[ RUN      ] ContainerizerType/DefaultContainerDNSFlagTest.ValidateFlag/0
[       OK ] ContainerizerType/DefaultContainerDNSFlagTest.ValidateFlag/0 (36 ms)
[ RUN      ] ContainerizerType/DefaultContainerDNSFlagTest.ValidateFlag/1
[       OK ] ContainerizerType/DefaultContainerDNSFlagTest.ValidateFlag/1 (41 ms)
[----------] 2 tests from ContainerizerType/DefaultContainerDNSFlagTest (79 ms total)

[----------] 1 test from IsolationFlag/CpuIsolatorTest
[ RUN      ] IsolationFlag/CpuIsolatorTest.ROOT_UserCpuUsage/0
[       OK ] IsolationFlag/CpuIsolatorTest.ROOT_UserCpuUsage/0 (834 ms)
[----------] 1 test from IsolationFlag/CpuIsolatorTest (865 ms total)

[----------] 1 test from IsolationFlag/MemoryIsolatorTest
[ RUN      ] IsolationFlag/MemoryIsolatorTest.ROOT_MemUsage/0
[       OK ] IsolationFlag/MemoryIsolatorTest.ROOT_MemUsage/0 (841 ms)
[----------] 1 test from IsolationFlag/MemoryIsolatorTest (871 ms total)

[----------] Global test environment tear-down
[==========] 936 tests from 92 test cases ran. (679359 ms total)
[  PASSED  ] 935 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] DockerContainerizerHealthCheckTest.ROOT_DOCKER_DockerHealthyTaskWithQuotedCommand

 1 FAILED TEST
  YOU HAVE 215 DISABLED TESTS

```

- [mesos-tests-stderr.log](http://dcos-win.westus.cloudapp.azure.com/mesos-build/review/66178/logs/mesos-tests-stderr.log):

```
I0320 21:56:40.184705  6296 master.cpp:10255] Updating the state of task cdc91fd7-3a79-4bd9-a20f-61faccf4d5bc
of framework 8fdf3455-3590-4df0-82ea-570c7d49b567-0000 (latest state: TASK_KILLED, status
update state: TASK_KILLED)
I0320 21:56:40.185685  8136 slave.cpp:3876] Shutting down framework 8fdf3455-3590-4df0-82ea-570c7d49b567-0000
I0320 21:56:40.185685  8136 slave.cpp:6569] Shutting down executor 'cdc91fd7-3a79-4bd9-a20f-61faccf4d5bc'
of framework 8fdf3455-3590-4df0-82ea-570c7d49b567-0000 at executor(1)@10.3.1.8:64467
I0320 21:56:40.186676  8136 slave.cpp:925] Agent terminating
W0320 21:56:40.186676  8136 slave.cpp:3872] IgnoriI0320 21:56:39.990691 11924 exec.cpp:162]
Version: 1.6.0
I0320 21:56:40.018695  9788 exec.cpp:236] Executor registered on agent 8fdf3455-3590-4df0-82ea-570c7d49b567-S0
I0320 21:56:40.023653  8572 executor.cpp:176] Received SUBSCRIBED event
I0320 21:56:40.027721  8572 executor.cpp:180] Subscribed executor on win-bld-srv-01.zq4gs31qjdiunm1ryi1452nvnh.dx.internal.cloudapp.net
I0320 21:56:40.028713  8572 executor.cpp:176] Received LAUNCH event
I0320 21:56:40.033659  8572 executor.cpp:648] Starting task cdc91fd7-3a79-4bd9-a20f-61faccf4d5bc
I0320 21:56:40.113693  8572 executor.cpp:483] Running 'D:\DCOS\mesos\src\mesos-containerizer.exe
launch <POSSIBLY-SENSITIVE-DATA>'
I0320 21:56:40.147699  8572 executor.cpp:661] Forked command at 948
I0320 21:56:40.187680 14164 exec.cpp:445] Executor asked to shutdown
I0320 21:56:40.187680 10120 executor.cpp:176] Received SHUTDOWN event
I0320 21:56:40.187680 10120 executor.cpp:758] Shutting down
I0320 21:56:40.188678 10120 executor.cpp:868] Sending SIGTERM to process tree at pid ng shutdown
framework 8fdf3455-3590-4df0-82ea-570c7d49b567-0000 because it is terminating
I0320 21:56:40.187680  6296 master.cpp:10354] Removing task cdc91fd7-3a79-4bd9-a20f-61faccf4d5bc
with resources cpus(allocated: *):4; mem(allocated: *):2048; disk(allocated: *):1024; ports(allocated:
*):[31000-32000] of framework 8fdf3455-3590-4df0-82ea-570c7d49b567-0000 on agent 8fdf3455-3590-4df0-82ea-570c7d49b567-S0
at slave(407)@10.3.1.8:62597 (win-bld-srv-01.zq4gs31qjdiunm1ryi1452nvnh.dx.internal.cloudapp.net)
I0320 21:56:40.189673  6296 master.cpp:1297] Agent 8fdf3455-3590-4df0-82ea-570c7d49b567-S0
at slave(407)@10.3.1.8:62597 (win-bld-srv-01.zq4gs31qjdiunm1ryi1452nvnh.dx.internal.cloudapp.net)
disconnected
I0320 21:56:40.189673  6296 master.cpp:3278] Disconnecting agent 8fdf3455-3590-4df0-82ea-570c7d49b567-S0
at slave(407)@10.3.1.8:62597 (win-bld-srv-01.zq4gs31qjdiunm1ryi1452nvnh.dx.internal.cloudapp.net)
I0320 21:56:40.189673  6296 master.cpp:3297] Deactivating agent 8fdf3455-3590-4df0-82ea-570c7d49b567-S0
at slave(407)@10.3.1.8:62597 (win-bld-srv-01.zq4gs31qjdiunm1ryi1452nvnh.dx.internal.cloudapp.net)
I0320 21:56:40.190672  6864 containerizer.cpp:2338] Destroying container ce67c839-675c-417b-a2d0-e9b94890b047
in RUNNING state
I0320 21:56:40.190672  2412 hierarchical.cpp:344] Removed framework 8fdf3455-3590-4df0-82ea-570c7d49b567-0000
I0320 21:56:40.190672  6864 containerizer.cpp:2952] Transitioning the state of container ce67c839-675c-417b-a2d0-e9b94890b047
from RUNNING to DESTROYING
I0320 21:56:40.190672  2412 hierarchical.cpp:766] Agent 8fdf3455-3590-4df0-82ea-570c7d49b567-S0
deactivated
I0320 21:56:40.191685  6864 launcher.cpp:156] Asked to destroy container ce67c839-675c-417b-a2d0-e9b94890b047
I0320 21:56:40.249722 12720 containerizer.cpp:2791] Container ce67c839-675c-417b-a2d0-e9b94890b047
has exited
I0320 21:56:40.282680 12260 master.cpp:1139] Master terminating
I0320 21:56:40.284689  8136 hierarchical.cpp:609] Removed agent 8fdf3455-3590-4df0-82ea-570c7d49b567-S0
I0320 21:56:41.246773 13200 process.cpp:929] Stopped the socket accept loop
```

- Mesos Reviewbot Windows


On March 20, 2018, 6:36 p.m., Meng Zhu wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66178/
> -----------------------------------------------------------
> 
> (Updated March 20, 2018, 6:36 p.m.)
> 
> 
> Review request for mesos, Chun-Hung Hsiao and Greg Mann.
> 
> 
> Bugs: MESOS-8617 and MESOS-8624
>     https://issues.apache.org/jira/browse/MESOS-8617
>     https://issues.apache.org/jira/browse/MESOS-8624
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> Agent should launch the task in their receiving order.
> On the task launch path, there are currently two
> asynchronous steps which may complete out of order:
> unschedule GC and task authorization.
> 
> This test simulates the reordering of the completions
> of task authorization step and verify that, despite the
> reordering, tasks can still launch in their original order.
> 
> 
> Diffs
> -----
> 
>   src/tests/mesos.hpp 2c3d0c9350bbbbcd2223ff20c0797d1849d38c19 
>   src/tests/mesos.cpp d82963195573dd9ed7d12a7708f64a236b28cdf1 
>   src/tests/slave_tests.cpp f76500ebdb67f131a57a3b5aaae8c952d019e354 
> 
> 
> Diff: https://reviews.apache.org/r/66178/diff/1/
> 
> 
> Testing
> -------
> 
> make check
> 
> 
> Thanks,
> 
> Meng Zhu
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message