-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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] ThreadPoolTests testScheduledFixedDelayRejection failing #106618
Comments
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Started failing recently. |
👍 looks flaky since it was introduced yesterday; muted on |
Ok yeah this test doesn't quite work. The problem is that we need the scheduled task to be rejected, but because it's racing with the blocking tasks it might end up in the queue and therefore it never runs. |
Not really necessary to allow the scheduled task to race against the blocks, and this race is a source of test flakiness. Fixed by imposing the blocks first. Closes elastic#106618
Just a test bug --> low-risk |
Not really necessary to allow the scheduled task to race against the blocks, and this race is a source of test flakiness. Fixed by imposing the blocks first. Closes #106618
Not really necessary to allow the scheduled task to race against the blocks, and this race is a source of test flakiness. Fixed by imposing the blocks first. Closes elastic#106618
Not really necessary to allow the scheduled task to race against the blocks, and this race is a source of test flakiness. Fixed by imposing the blocks first. Closes elastic#106618
This test was introduced in #106542
Build scan:
https://gradle-enterprise.elastic.co/s/vhbjdbibh2se2/tests/:server:test/org.elasticsearch.threadpool.ThreadPoolTests/testScheduledFixedDelayRejection
Reproduction line:
Applicable branches:
main
Reproduces locally?:
Didn't try
Failure history:
Failure dashboard for
org.elasticsearch.threadpool.ThreadPoolTests#testScheduledFixedDelayRejection
Failure excerpt:
The text was updated successfully, but these errors were encountered: