Skip to content

[CI] ThreadPoolMergeSchedulerTests testSchedulerCloseWaitsForRunningMerge failing #125236

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.

Sign up for GitHub

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

Jump to bottom
Open
elasticsearchmachine opened this issue Mar 19, 2025 · 4 comments · Fixed by #126110
Open

[CI] ThreadPoolMergeSchedulerTests testSchedulerCloseWaitsForRunningMerge failing #125236

elasticsearchmachine opened this issue Mar 19, 2025 · 4 comments · Fixed by #126110
Assignees
@albertzaharovits
Labels
:Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Indexing Meta label for Distributed Indexing team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Mar 19, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":server:test" --tests "org.elasticsearch.index.engine.ThreadPoolMergeSchedulerTests.testSchedulerCloseWaitsForRunningMerge" -Dtests.seed=AC984A9BB73DF1FC -Dtests.configure_test_clusters_with_one_processor=true -Dtests.locale=mg -Dtests.timezone=Cuba -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: iterable containing [<Mock for OneMerge, hashCode: 469523963>]
     but: no item was <Mock for OneMerge, hashCode: 469523963>

Issue Reasons:

  • [main] 3 failures in test testSchedulerCloseWaitsForRunningMerge (6.7% fail rate in 45 executions)
  • [main] 2 failures in step part-1 (7.7% fail rate in 26 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (8.3% fail rate in 24 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. >test-failure Triaged test failures from CI labels Mar 19, 2025
elasticsearchmachine added a commit that referenced this issue Mar 19, 2025
@elasticsearchmachine
Mute org.elasticsearch.index.engine.ThreadPoolMergeSchedulerTests tes…
582fcaf 
…tSchedulerCloseWaitsForRunningMerge #125236
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 13 failures in test testSchedulerCloseWaitsForRunningMerge (7.6% fail rate in 170 executions)
  • [main] 2 failures in step part1 (9.1% fail rate in 22 executions)
  • [main] 11 failures in step part-1 (13.6% fail rate in 81 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (9.1% fail rate in 22 executions)
  • [main] 10 failures in pipeline elasticsearch-pull-request (13.5% fail rate in 74 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Distributed Indexing Meta label for Distributed Indexing team labels Mar 19, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-distributed-indexing (Team:Distributed Indexing)

@tlrx
Copy link
Member

tlrx commented Mar 20, 2025

@albertzaharovits looks low priority to me, I wonder if the test should signal that the merge effectively started before closing the threadPoolMergeScheduler.

@tlrx tlrx added the low-risk An open issue or test failure that is a low risk to future releases label Mar 20, 2025
@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Mar 20, 2025
smalyshev pushed a commit to smalyshev/elasticsearch that referenced this issue Mar 21, 2025
@elasticsearchmachine @smalyshev
Mute org.elasticsearch.index.engine.ThreadPoolMergeSchedulerTests tes…
ddbf943 
…tSchedulerCloseWaitsForRunningMerge elastic#125236
omricohenn pushed a commit to omricohenn/elasticsearch that referenced this issue Mar 28, 2025
@elasticsearchmachine @omricohenn
Mute org.elasticsearch.index.engine.ThreadPoolMergeSchedulerTests tes…
b41b4d5 
…tSchedulerCloseWaitsForRunningMerge elastic#125236
@albertzaharovits albertzaharovits self-assigned this Apr 2, 2025
@albertzaharovits albertzaharovits mentioned this issue Apr 2, 2025
Merged
albertzaharovits added a commit that referenced this issue Apr 3, 2025
@albertzaharovits
Fix ThreadPoolMergeSchedulerTests testSchedulerCloseWaitsForRunningMe…
ecaa0b1 
…rge (#126110)

Fixes #125236
elasticsearchmachine added a commit that referenced this issue Apr 3, 2025
@elasticsearchmachine
Mute org.elasticsearch.index.engine.ThreadPoolMergeSchedulerTests tes…
3277ff8 
…tSchedulerCloseWaitsForRunningMerge #125236
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test testSchedulerCloseWaitsForRunningMerge (6.7% fail rate in 45 executions)
  • [main] 2 failures in step part-1 (7.7% fail rate in 26 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (8.3% fail rate in 24 executions)

Build Scans:

andreidan pushed a commit to andreidan/elasticsearch that referenced this issue Apr 9, 2025
@albertzaharovits @andreidan
Fix ThreadPoolMergeSchedulerTests testSchedulerCloseWaitsForRunningMe…
5e07bf6 
…rge (elastic#126110)

Fixes elastic#125236
andreidan pushed a commit to andreidan/elasticsearch that referenced this issue Apr 9, 2025
@elasticsearchmachine @andreidan
Mute org.elasticsearch.index.engine.ThreadPoolMergeSchedulerTests tes…
2bc277d 
…tSchedulerCloseWaitsForRunningMerge elastic#125236
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@albertzaharovits albertzaharovits

Labels
:Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Indexing Meta label for Distributed Indexing team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
3 participants
@tlrx @albertzaharovits @elasticsearchmachine