Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the clock resolution to millis in ScheduledEventTests #38516

Conversation

droberts195
Copy link
Contributor

The clock resolution changed from jdk8 to jdk10, hence the
test is passing in jdk8 but failing in jdk10. Scheduled
events are serialised and deserialised with millisecond
precision, making test fail in jdk 10 and higher.

Fixes a problem introduced by #38415 and the fix is
identical to the one that was made in #38405.

Backport of #38506

)

The clock resolution changed from jdk8 to jdk10, hence the
test is passing in jdk8 but failing in jdk10.  Scheduled
events are serialised and deserialised with millisecond
precision, making test fail in jdk 10 and higher.

Fixes a problem introduced by elastic#38415 and the fix is
identical to the one that was made in elastic#38405.
@droberts195 droberts195 added :ml Machine learning backport labels Feb 6, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core

@droberts195 droberts195 changed the title Fix the clock resolution to millis in ScheduledEventTests (#38506) Fix the clock resolution to millis in ScheduledEventTests Feb 6, 2019
@droberts195
Copy link
Contributor Author

Closing, as the change was incorporated in #38513, so the change is in the 7.x branch via that PR

@droberts195 droberts195 closed this Feb 8, 2019
@droberts195 droberts195 deleted the millisecond_accuracy_for_scheduled_event_tests_7x branch November 29, 2021 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :ml Machine learning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants