-
Notifications
You must be signed in to change notification settings - Fork 25k
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
[CI] NodeStatsMonitoringDocTests#testToUTC fails #38359
Labels
Comments
cbuescher
added
>test-failure
Triaged test failures from CI
:Data Management/Monitoring
labels
Feb 4, 2019
Pinging @elastic/es-core-features |
Another one:
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/1828/console |
I got one more in a PR run - still doesn't reproduce locally
|
to be fair, this test does not adds more coverage. |
pgomulka
added a commit
that referenced
this issue
Feb 11, 2019
The test was relying on toString in ZonedDateTime which is different to what is formatted by strict_date_time when milliseconds are 0 The method is just delegating to dateFormatter, so that scenario should be covered there. closes #38359
pgomulka
added a commit
to pgomulka/elasticsearch
that referenced
this issue
Feb 11, 2019
The test was relying on toString in ZonedDateTime which is different to what is formatted by strict_date_time when milliseconds are 0 The method is just delegating to dateFormatter, so that scenario should be covered there. closes elastic#38359
pgomulka
added a commit
to pgomulka/elasticsearch
that referenced
this issue
Feb 11, 2019
The test was relying on toString in ZonedDateTime which is different to what is formatted by strict_date_time when milliseconds are 0 The method is just delegating to dateFormatter, so that scenario should be covered there. closes elastic#38359
This was referenced Feb 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/1812/console
Couldn't reproduce locally but looks like a date formatting issue.
The text was updated successfully, but these errors were encountered: