You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Bannier (JIRA)" <ji...@apache.org> on 2018/09/07 14:06:00 UTC

[jira] [Created] (MESOS-9218) StorageLocalResourceProviderTest.ROOT_PublishUnpublishResourcesPluginKilled is flaky

Benjamin Bannier created MESOS-9218:
---------------------------------------

             Summary: StorageLocalResourceProviderTest.ROOT_PublishUnpublishResourcesPluginKilled is flaky
                 Key: MESOS-9218
                 URL: https://issues.apache.org/jira/browse/MESOS-9218
             Project: Mesos
          Issue Type: Bug
          Components: test
    Affects Versions: 1.8.0
         Environment: ubuntu-16.04-cmake-default
            Reporter: Benjamin Bannier
         Attachments: consoleText.txt

We observed a test flake in {{StorageLocalResourceProviderTest.ROOT_PublishUnpublishResourcesPluginKilled}} in our CI while testing {{master}} (aka {{c9c2be8982d3585994493dab9916c89deb61ec48}}). I have not confirmed whether this also affects {{1.7.x}}.

The test fails with
{noformat}
I../../src/tests/storage_local_resource_provider_tests.cpp:2644: Failure
Failed to wait 15secs for taskStarting
../../src/tests/storage_local_resource_provider_tests.cpp:2625: Failure
Actual function call count doesn't match EXPECT_CALL(sched, statusUpdate(&driver, _))...
         Expected: to be called 3 times
           Actual: never called - unsatisfied and active
0907 11:27:01.616554 20248 hierarchical.cpp:2386] Filtered offer with cpus:2; mem:1024; disk:1024; ports:[31000-32000] on agent 668232c7-f20c-4219-a829-b45e294a3181-S0 for role storage of framework 668232c7-f20c-4219-a829-b45e294a3181-0000
../../src/tests/storage_local_resource_provider_tests.cpp:2631: Failure
Actual function call count doesn't match EXPECT_CALL(sched, resourceOffers(&driver, OffersHaveResource( persistentVolume)))...
         Expected: to be called once
           Actual: never called - unsatisfied and active
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)