HomeMesosphereNo notifications. 4 unresolved issues.

Use event timestamp in GracefulTaskKillIntegrationTest.
ClosedAll Users

Authored by jeschkies on Jun 6 2017, 1:29 PM.

Details

Summary

The tests fails sometimes with "4160 was not less than 4000". Since we
take the receive time stamp after it was processed by the test we might
have some delay. To avoid the extra cost we'll take the timestamp when
the event was received by Marathon.

Test Plan

sbt integration:test

Diff Detail

Repository
rMARATHON marathon
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
jeschkies created this revision.Jun 6 2017, 1:29 PM
jenkins accepted this revision.Jun 6 2017, 1:48 PM
This revision is now accepted and ready to land.Jun 6 2017, 1:48 PM
✔ Build of 3417 completed jenkins-public-marathon-phabricator-162.

You can create a DC/OS with your patched Marathon by creating a new pull
request with the following changes in buildinfo.json:

"url": "https://downloads.mesosphere.io/marathon/snapshots/marathon-1.5.0-SNAPSHOT-560-g9f6aaec.tgz",
"sha1"" "14b43170d9fccab686de0432a690f4a2c257067f"

\\ ٩( ᐛ )و //

jeschkies added 1 JIRA issue(s): MARATHON-7468.Jun 6 2017, 3:27 PM
ichernetsky accepted this revision.Jun 7 2017, 6:55 PM
timcharper accepted this revision.Jun 8 2017, 5:25 AM

Brilliant. 5 stars.

This revision was automatically updated to reflect the committed changes.

Brilliant. 5 stars.

Thanks. I still think there is some chance that we might be over 4000ms but it's less likely now :).