Skip to content

[CI] ScriptDocValuesDatesTests.testJodaTimeBwc fails reproducibly #32779

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

Closed
spinscale opened this issue Aug 10, 2018 · 2 comments · Fixed by #32798
Closed

[CI] ScriptDocValuesDatesTests.testJodaTimeBwc fails reproducibly #32779

spinscale opened this issue Aug 10, 2018 · 2 comments · Fixed by #32798
Labels
:Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI

Comments

@spinscale
Copy link
Contributor

This test fails reproducible with this seed for me under osx and the master branch:

./gradlew :server:test -Dtests.seed=3F07B06B4ACEACD6 -Dtests.class=org.elasticsearch.index.fielddata.ScriptDocValuesDatesTests -Dtests.method="testJodaTimeBwc" -Dtests.security.manager=true -Dtests.locale=hi -Dtests.timezone=Africa/Monrovia

Failed under Linux in CI, see https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=fedora/2610/console

@rjernst could you take a look, please?

@spinscale spinscale added :Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI labels Aug 10, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@spinscale
Copy link
Contributor Author

rjernst added a commit to rjernst/elasticsearch that referenced this issue Aug 11, 2018
This commit adds a guard around the rare case that no documents in the
10 iterations actually have any values, thus making the warning check
incorrect.

closes elastic#32779
rjernst added a commit that referenced this issue Sep 16, 2018
This commit adds a guard around the rare case that no documents in the
10 iterations actually have any values, thus making the warning check
incorrect.

closes #32779
rjernst added a commit that referenced this issue Sep 16, 2018
This commit adds a guard around the rare case that no documents in the
10 iterations actually have any values, thus making the warning check
incorrect.

closes #32779
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants