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 70368: Initialized resource provider manager earlier when recovering.
Date Tue, 09 Apr 2019 18:29:44 GMT

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



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

Reviews applied: `['70367', '70368']`

Failed command: `Start-MesosCITesting`

All the build artifacts available at: http://dcos-win.westus2.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/3127/mesos-review-70368

Relevant logs:

- [mesos-tests.log](http://dcos-win.westus2.cloudapp.azure.com/artifacts/mesos-reviewbot-testing/3127/mesos-review-70368/logs/mesos-tests.log):

```
I0409 18:29:27.014086 38016 master.cpp:1295] Agent 60837767-0d93-463d-818b-9b240ad3dba6-S0
at slave(501)@192.10.1.4:53871 (windows-01.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net)
disconnected
I0409 18:29:27.014086 38016 master.cpp:3333] Disconnecting agent 60837767-0d93-463d-818b-9b240ad3dba6-S0
at slave(501)@192.10.1.4:53871 (windows-01.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net)
I0409 18:29:27.014086 38016 master.cpp:3352] Deactivating agent 60837767-0d93-463d-818b-9b240ad3dba6-S0
at slave(501)@192.10.1.4:53871 (windows-01.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net)
I0409 18:29:27.015076 41052 hierarchical.cpp:392] Removed framework 60837767-0d93-463d-818b-9b240ad3dba6-0000
I0409 18:29:27.015076 44084 containerizer.cpp:2576] Destroying container c6b3de4c-613f-4fd7-9dc6-e2e318752d24
in RUNNING state
I0409 18:29:27.015076 41052 hierarchical.cpp:829] Agent 60837767-0d93-463d-818b-9b240ad3dba6-S0
deactivated
I0409 18:29:27.015076 44084 containerizer.cpp:3278] Transitioning the state of container c6b3de4c-613f-4fd7-9dc6-e2e318752d24
from RUNNING to DESTROYING
I0409 18:29:27.016124 44084 launcher.cpp:161] Asked to destroy container c6b[       OK ] IsolationFlag/MemoryIsolatorTest.ROOT_MemUsage/0
(773 ms)
[----------] 1 test from IsolationFlag/MemoryIsolatorTest (792 ms total)

[----------] Global test environment tear-down
[==========] 1159 tests from 108 test cases ran. (586553 ms total)
[  PASSED  ] 1157 tests.
[  FAILED  ] 2 tests, listed below:
[  FAILED  ] DockerFetcherPluginTest.INTERNET_CURL_FetchImage
[  FAILED  ] DockerFetcherPluginTest.INTERNET_CURL_InvokeFetchByName

 2 FAILED TESTS
  YOU HAVE 233 DISABLED TESTS

3de4c-613f-4fd7-9dc6-e2e318752d24
W0409 18:29:27.017072 43960 process.cpp:1423] Failed to recv on socket WindowsFD::Type::SOCKET=9676
to peer '192.10.1.4:56253': IO failed with error code: The specified network name is no longer
available.

W0409 18:29:27.018090 43960 process.cpp:838] Failed to recv on socket WindowsFD::Type::SOCKET=7988
to peer '192.10.1.4:56254': IO failed with error code: The specified network name is no longer
available.

I0409 18:29:27.050192 38016 containerizer.cpp:3117] Container c6b3de4c-613f-4fd7-9dc6-e2e318752d24
has exited
I0409 18:29:27.082119 32644 master.cpp:1135] Master terminating
I0409 18:29:27.083086 38824 hierarchical.cpp:680] Removed agent 60837767-0d93-463d-818b-9b240ad3dba6-S0
I0409 18:29:27.680088 43960 process.cpp:927] Stopped the socket accept loop
```

- Mesos Reviewbot Windows


On April 9, 2019, 12:24 p.m., Benjamin Bannier wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/70368/
> -----------------------------------------------------------
> 
> (Updated April 9, 2019, 12:24 p.m.)
> 
> 
> Review request for mesos, Chun-Hung Hsiao and Greg Mann.
> 
> 
> Bugs: MESOS-9667
>     https://issues.apache.org/jira/browse/MESOS-9667
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> When recovering and reusing the same agent ID the resource provider
> manager can be initialized before e.g., recovering executors. This patch
> move the initialization to such an earlier point. This e.g., allows to
> successfully publish resources via the manager when HTTP-based executors
> resubscribe which previously ran into an assertion failure.
> 
> If the agent ID is not reused we still need to wait for the agent to
> register with the master which would assign an agent ID. In that case we
> do not expect any executors to resubscribe.
> 
> 
> Diffs
> -----
> 
>   src/slave/slave.cpp 5373cee5d30c2403497939eeba2ee5405117237e 
>   src/tests/slave_tests.cpp 528a25a837513f153de2a5e89897440144385633 
> 
> 
> Diff: https://reviews.apache.org/r/70368/diff/3/
> 
> 
> Testing
> -------
> 
> * `make check`
> * the test fails without the agent change
> * ran the test for 17000 iterations without failures (failure rate <1% with 66% certainty)
> 
> 
> Thanks,
> 
> Benjamin Bannier
> 
>


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