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

[CI] Failure of org.elasticsearch.common.logging.EvilLoggerTests testDeprecatedSettings #25498

Closed
droberts195 opened this issue Jun 30, 2017 · 2 comments
Assignees
Labels
>test Issues or PRs that are addressing/adding tests

Comments

@droberts195
Copy link
Contributor

Console log: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+5.x+multijob-unix-compatibility/os=ubuntu/927/console

Stack:

FAILURE 0.04s J0 | EvilLoggerTests.testDeprecatedSettings <<< FAILURES!
   > Throwable #1: java.lang.AssertionError: 
   > Expected: <1>
   >      but: was <0>
   > 	at __randomizedtesting.SeedInfo.seed([996F8227E4E1FD0B:F91679FDCF0EEB84]:0)
   > 	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
   > 	at org.elasticsearch.common.logging.EvilLoggerTests.testDeprecatedSettings(EvilLoggerTests.java:271)
   > 	at java.lang.Thread.run(Thread.java:748)

Repro command:

gradle :qa:evil-tests:test -Dtests.seed=996F8227E4E1FD0B -Dtests.class=org.elasticsearch.common.logging.EvilLoggerTests -Dtests.method="testDeprecatedSettings" -Dtests.security.manager=false -Dtests.locale=es-US -Dtests.timezone=Asia/Beirut

This does not reproduce for me.

I wonder if the problem is not actually in the test that is failing but in some sort of unfinished processing that is still in progress when the concurrent test that was recently added in 11f491d completes?

@droberts195 droberts195 added the >test Issues or PRs that are addressing/adding tests label Jun 30, 2017
@jasontedor
Copy link
Member

It's really unclear to me what happened here, and this has not reproduced since, and did not reproduce for me after 4096 executions. I do not think the two tests interfered with each other as they use separate temporary directories and independent loggers. I did push fe04b66 so that we can see the actual logging here in case this occurs again. I'm going to close this for now, if we see this occur again I will take a deeper look.

@jasontedor
Copy link
Member

jasontedor commented Aug 15, 2017

This one did not reproduce because it relied on another test running the same JVM before the failing test here. See #25680 for all the gory details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>test Issues or PRs that are addressing/adding tests
Projects
None yet
Development

No branches or pull requests

2 participants