[
https://issues.apache.org/jira/browse/MESOS-8976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596700#comment-16596700
]
Chun-Hung Hsiao commented on MESOS-8976:
----------------------------------------
This is caused by MESOS-6231. The following
[code|https://github.com/apache/mesos/blob/959fa0bbe6dcde60262bc131f851f5bb2d709d57/src/tests/utils.cpp#L59-L67]
is stuck because the {{/metrics/snapshot}} is pending for more than 1hr:
{code:cpp}
// TODO(neilc): This request might timeout if the current value of a
// metric cannot be determined. In tests, a common cause for this is
// MESOS-6231 when multiple scheduler drivers are in use.
Future<http::Response> response = http::get(upid, "snapshot");
AWAIT_EXPECT_RESPONSE_STATUS_EQ(http::OK().status, response);
AWAIT_EXPECT_RESPONSE_HEADER_EQ(APPLICATION_JSON, "Content-Type", response);
Try<JSON::Object> parse = JSON::parse<JSON::Object>(response->body);
{code}
> MasterTest.LaunchDuplicateOfferLost is flaky
> --------------------------------------------
>
> Key: MESOS-8976
> URL: https://issues.apache.org/jira/browse/MESOS-8976
> Project: Mesos
> Issue Type: Bug
> Reporter: Benno Evers
> Priority: Major
> Labels: flaky-test
> Attachments: LaunchDuplicateOfferLost.jenkins-faillog
>
>
> In an internal CI run, we observed a failure with this test where the
> scheduler seemed to be stuck repeatedly allocating resources to the agent for
> about 1 hour before getting timed out. See attached log for details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
