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] RejectionActionIT testSimulatedSearchRejectionLoad failing #125901

Open
elasticsearchmachine opened this issue Mar 30, 2025 · 2 comments
Open
Labels
:Delivery/Build Build or test infrastructure needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Mar 30, 2025

Build Scans:

Reproduction Line:

./gradlew ":server:internalClusterTest" --tests "org.elasticsearch.action.RejectionActionIT.testSimulatedSearchRejectionLoad" -Dtests.seed=FF616FD548F0752A -Dtests.jvm.argline="-Des.entitlements.enabled=true" -Dtests.locale=el-CY -Dtests.timezone=Canada/Newfoundland -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: There are still [5] in-flight contexts. The first one's creation site is listed as the cause of this exception.

Issue Reasons:

  • [main] 2 consecutive failures in test testSimulatedSearchRejectionLoad
  • [main] 10 failures in test testSimulatedSearchRejectionLoad (3.4% fail rate in 291 executions)
  • [main] 2 failures in step concurrent-search-tests (40.0% fail rate in 5 executions)
  • [main] 4 failures in pipeline elasticsearch-periodic (50.0% fail rate in 8 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-platform-support (28.6% fail rate in 7 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.9% fail rate in 70 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Mar 30, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-delivery (Team:Delivery)

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 9 failures in test testSimulatedSearchRejectionLoad (3.1% fail rate in 290 executions)
  • [main] 2 failures in step concurrent-search-tests (40.0% fail rate in 5 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-platform-support (28.6% fail rate in 7 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.9% fail rate in 70 executions)
  • [main] 3 failures in pipeline elasticsearch-periodic (42.9% fail rate in 7 executions)

Build Scans:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

1 participant