[
https://issues.apache.org/jira/browse/MESOS-8976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596722#comment-16596722
]
Joseph Wu edited comment on MESOS-8976 at 8/29/18 6:52 PM:
-----------------------------------------------------------
The {{src/test/utils.cpp:64}} helper that failed is:
{code}
JSON::Object Metrics()
{
UPID upid("metrics", process::address());
/* For some reason, this call times out and never completes. */
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);
/* The `response->body` below is basically an unguarded `Future::get`
because the two AWAIT calls above are the EXPECT variety, meaning
that they do not return from the function when they fail. */
Try<JSON::Object> parse = JSON::parse<JSON::Object>(response->body);
CHECK_SOME(parse);
return parse.get();
}
{code}
was (Author: kaysoky):
The {{src/test/utils.cpp:64}} helper that failed is:
{code}
JSON::Object Metrics()
{
UPID upid("metrics", process::address());
/* For some reason, this call times out and never completes. */
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);
/* The `response->body` below is basically an unguarded `Future::get` because
the
two AWAIT calls above are the EXPECT variety, meaning that they do not
return
from the function when they fail. */
Try<JSON::Object> parse = JSON::parse<JSON::Object>(response->body);
CHECK_SOME(parse);
return parse.get();
}
{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)
