-
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] ListenableActionFutureTests.testListenersNotifiedOnCorrectThreads failed #68772
Comments
Pinging @elastic/es-distributed (Team:Distributed) |
@DaveCTurner you mind taking a look here since you recently authored this test? |
Since this test was just added and has already failed I went ahead and muted it in |
Ugh. Thanks Mark, I'll mute it on 7.x too and investigate tomorrow. |
Thanks, David. |
I left this running in a loop overnight and it failed similarly for me after ~100k runs. I think this means that I don't see much that might explain this until I get down to |
This test fails pretty reliably:
I think that's bad, right? |
No, it's ok, |
This test assumed, incorrectly, that `future#done()` completes before `future#set()` returns, but this isn't true if there are multiple threads racing to complete the future. In other words listeners added before calling `onResponse()` are not necessarily notified by the time `onResponse()` returns. This commit fixes the test to account for this subtle point. Closes elastic#68772
This test assumed, incorrectly, that `future#done()` completes before `future#set()` returns, but this isn't true if there are multiple threads racing to complete the future. In other words listeners added before calling `onResponse()` are not necessarily notified by the time `onResponse()` returns. This commit fixes the test to account for this subtle point. Closes #68772
This test assumed, incorrectly, that `future#done()` completes before `future#set()` returns, but this isn't true if there are multiple threads racing to complete the future. In other words listeners added before calling `onResponse()` are not necessarily notified by the time `onResponse()` returns. This commit fixes the test to account for this subtle point. Closes #68772
This looks like a newly added test.
Build scan:
https://gradle-enterprise.elastic.co/s/benbyofejft46/tests/:server:test/org.elasticsearch.action.support.ListenableActionFutureTests/testListenersNotifiedOnCorrectThreads#1
Repro line:
./gradlew ':server:test' --tests "org.elasticsearch.action.support.ListenableActionFutureTests.testListenersNotifiedOnCorrectThreads" -Dtests.seed=6F4C360FA7AEA154 -Dtests.security.manager=true -Dtests.locale=und -Dtests.timezone=America/Panama -Druntime.java=11
Reproduces locally?:
Nope.
Applicable branches:
Only
master
so far.Failure history:
https://gradle-enterprise.elastic.co/scans/tests?search.relativeStartTime=P7D&search.timeZoneId=America/Los_Angeles&tests.container=org.elasticsearch.action.support.ListenableActionFutureTests&tests.disabledDistributions=WyJvdXRjb21lOnNraXBwZWQiXQ&tests.sortField=FAILED&tests.test=testListenersNotifiedOnCorrectThreads&tests.unstableOnly=true
Failure excerpt:
The text was updated successfully, but these errors were encountered: