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.
Details
Details
- Reviewers
timcharper unterstein jenkins ichernetsky - Commits
- rMARATHONe1fe7aad32c9: Use event timestamp in GracefulTaskKillIntegrationTest.
rMARATHON916a21fb868a: Use event timestamp in GracefulTaskKillIntegrationTest.
rMARATHON0f33f606106c: Use event timestamp in GracefulTaskKillIntegrationTest.
rMARATHON6b56b1348346: Use event timestamp in GracefulTaskKillIntegrationTest. (#5430) - JIRA Issues
- JIRA MARATHON-7468 GracefulTaskKillIntegrationTest Fails With "4xxx was not less than 4000"
sbt integration:test
Diff Detail
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.
Comment Actions
✔ 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"
\\ ٩( ᐛ )و //
Comment Actions
Thanks. I still think there is some chance that we might be over 4000ms but it's less likely now :).