Fixed timeformat that introduced flaky tests depending on time #11652
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsvd
reviewed
Mar 4, 2020
jsvd
approved these changes
Mar 4, 2020
andsel
force-pushed
the
fix/datetime_format_in_monitoring
branch
from
c344099
to
3484dd8
Compare
|
Andrea Selva merged this into the following branches!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With PR #11541 we formated the date_time field to be pushed to ES with bad format, used
%kinstead of%H, so in some cases (when hour < 10AM) generating hour with space instead of padding 0, for example...T 8:...instead of..T08:...