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 69942: Added a test for MESOS-9554.
Date Mon, 11 Feb 2019 19:33:36 GMT

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



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

Reviews applied: `['69900', '69902', '69942']`

Failed command: `Start-MesosCITesting`

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

Relevant logs:

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

```
W0211 19:33:19.789881 41488 slave.cpp:3934] Ignoring shutdown framework 0e08c1e8-6346-4bce-bd53-64c57bdab0cb-0000
because it is terminating
I0211 19:33:19.791877 43452 hierarchical.cpp:358] Removed framework 0e08c1e8-6346-4bce-bd53-64c57bdab0cb-0000
I0211 19:33:19.792883 37668 master.cpp:1269] Agent 0e08c1e8-6346-4bce-bd53-64c57bdab0cb-S0
at slave(477)@192.10.1.6:60203 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net)
disconnected
I0211 19:33:19.792883 37668 master.cpp:3272] Disconnecting agent 0e08c1e8-6346-4bce-bd53-64c57bdab0cb-S0
at slave(477)@192.10.1.6:60203 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net)
I0211 19:33:19.792883 37668 master.cpp:3291] Deactivating agent 0e08c1e8-6346-4bce-bd53-64c57bdab0cb-S0
at slave(477)@192.10.1.6:60203 (windows-02.chtsmhjxogyevckjfayqqcnjda.xx.internal.cloudapp.net)
I0211 19:33:19.792883 41488 hierarchical.cpp:793] Agent 0e08c1e8-6346-4bce-bd53-64c57bdab0cb-S0
deactivated
I0211 19:33:19.793946 41488 containerizer.cpp:2477] Destroying container 00a47ff7-873c-4085-978b-485cbca4089f
in RUNNING state
I0211 19:33:19.793946 41488 containerizer.cpp:3144] Transitioning the state of container 00a47ff7-873c-4085-978b-485cbca4089f
from RUNNING to DESTROYING
I0211 19:33:19.794879 41488 launcher.cpp:161] Asked to destroy container 00a47ff7-873c-4085-978b-485cbca4089f
W0211 19:33:19.795878 43388 process.cpp[       OK ] IsolationFlag/MemoryIsolatorTest.ROOT_MemUsage/0
(688 ms)
[----------] 1 test from IsolationFlag/MemoryIsolatorTest (706 ms total)

[----------] Global test environment tear-down
[==========] 1096 tests from 104 test cases ran. (514431 ms total)
[  PASSED  ] 1095 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] DockerFetcherPluginTest.INTERNET_CURL_InvokeFetchByName

 1 FAILED TEST
  YOU HAVE 231 DISABLED TESTS

:1423] Failed to recv on socket WindowsFD::Type::SOCKET=6532 to peer '192.10.1.6:62100': IO
failed with error code: The specified network name is no longer available.

W0211 19:33:19.796885 43388 process.cpp:838] Failed to recv on socket WindowsFD::Type::SOCKET=8316
to peer '192.10.1.6:62101': IO failed with error code: The specified network name is no longer
available.

I0211 19:33:19.815894 44752 containerizer.cpp:2983] Container 00a47ff7-873c-4085-978b-485cbca4089f
has exited
I0211 19:33:19.844877 40992 master.cpp:1109] Master terminating
I0211 19:33:19.846884 41488 hierarchical.cpp:644] Removed agent 0e08c1e8-6346-4bce-bd53-64c57bdab0cb-S0
I0211 19:33:20.391891 43388 process.cpp:927] Stopped the socket accept loop
```

- Mesos Reviewbot Windows


On Feb. 11, 2019, 6:21 p.m., Benjamin Mahler wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69942/
> -----------------------------------------------------------
> 
> (Updated Feb. 11, 2019, 6:21 p.m.)
> 
> 
> Review request for mesos, Benjamin Bannier and Meng Zhu.
> 
> 
> Bugs: MESOS-9554
>     https://issues.apache.org/jira/browse/MESOS-9554
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> This test ensures that the framework allocation loop does not
> incorrectly break in the case that a framework is incapable
> of receiving the resources on an agent. In this case, the loop
> should continue as other frameworks may be capable of receiving
> the resources.
> 
> 
> Diffs
> -----
> 
>   src/tests/hierarchical_allocator_tests.cpp cc88afbad1b4e6bf707cb13b50c964aa01f9a3ee

> 
> 
> Diff: https://reviews.apache.org/r/69942/diff/1/
> 
> 
> Testing
> -------
> 
> Ensured it fails on master, succeeds after fix to MESOS-9554.
> 
> Ran in repetition.
> 
> 
> Thanks,
> 
> Benjamin Mahler
> 
>


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