-
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] PrioritizedThrottledTaskRunnerTests testEnqueueSpawnsNewTasksUpToMax failing #92910
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
>test-failure
Triaged test failures from CI
Comments
slobodanadamovic
added
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>test-failure
Triaged test failures from CI
labels
Jan 13, 2023
Pinging @elastic/es-distributed (Team:Distributed) |
fcofdez
added a commit
to fcofdez/elasticsearch
that referenced
this issue
Jan 23, 2023
This should help debugging elastic#92910 and rule out possible enviromental issues, such us slowness creating threads due to an overloaded CI worker.
fcofdez
added a commit
to fcofdez/elasticsearch
that referenced
this issue
Jan 30, 2023
fcofdez
added a commit
that referenced
this issue
Jan 30, 2023
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Feb 2, 2023
These tests try and execute `maxThreads` concurrent tasks to ensure that the rest of the executor's queue has been processed, but due to elastic#93443 (and the executor's zero timeout) this sometimes doesn't work. This commit fixes the problem by making every thread a core thread so that they do not time out. Closes elastic#92910
DaveCTurner
added a commit
that referenced
this issue
Feb 2, 2023
These tests try and execute `maxThreads` concurrent tasks to ensure that the rest of the executor's queue has been processed, but due to #93443 (and the executor's zero timeout) this sometimes doesn't work. This commit fixes the problem by making every thread a core thread so that they do not time out. Closes #92910 Closes #92747
mark-vieira
pushed a commit
to mark-vieira/elasticsearch
that referenced
this issue
Feb 2, 2023
These tests try and execute `maxThreads` concurrent tasks to ensure that the rest of the executor's queue has been processed, but due to elastic#93443 (and the executor's zero timeout) this sometimes doesn't work. This commit fixes the problem by making every thread a core thread so that they do not time out. Closes elastic#92910 Closes elastic#92747
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
>test-failure
Triaged test failures from CI
Build scan:
https://gradle-enterprise.elastic.co/s/4zkxhhdho2i6a/tests/:server:test/org.elasticsearch.common.util.concurrent.PrioritizedThrottledTaskRunnerTests/testEnqueueSpawnsNewTasksUpToMax
Reproduction line:
Applicable branches:
main
Reproduces locally?:
Didn't try
Failure history:
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.common.util.concurrent.PrioritizedThrottledTaskRunnerTests&tests.test=testEnqueueSpawnsNewTasksUpToMax
Failure excerpt:
The text was updated successfully, but these errors were encountered: