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] RollingUpgradeSearchableSnapshotIndexCompatibilityIT testSearchableSnapshotUpgrade {p0=[9.0.0, 9.0.0, 9.0.0]} failing #119990

Closed
elasticsearchmachine opened this issue Jan 10, 2025 · 2 comments · Fixed by #120113
Labels
:Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. 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 Jan 10, 2025

Build Scans:

Reproduction Line:

./gradlew ":qa:lucene-index-compatibility:javaRestTest" --tests "org.elasticsearch.lucene.RollingUpgradeSearchableSnapshotIndexCompatibilityIT" -Dtests.method="testSearchableSnapshotUpgrade {p0=[9.0.0, 9.0.0, 9.0.0]}" -Dtests.seed=28A53320AA0C74AE -Dtests.locale=es-ES -Dtests.timezone=America/Santo_Domingo -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.RuntimeException: An error occurred while checking cluster 'test-cluster' status.

Issue Reasons:

  • [main] 16 consecutive failures in test testSearchableSnapshotUpgrade {p0=[9.0.0, 9.0.0, 9.0.0]}
  • [main] 7 consecutive failures in step part1
  • [main] 9 consecutive failures in step part-1
  • [main] 2 consecutive failures in step release-tests
  • [main] 7 consecutive failures in pipeline elasticsearch-intake
  • [main] 9 consecutive failures in pipeline elasticsearch-pull-request
  • [main] 18 failures in test testSearchableSnapshotUpgrade {p0=[9.0.0, 9.0.0, 9.0.0]} (3.3% fail rate in 547 executions)
  • [main] 7 failures in step part1 (6.5% fail rate in 108 executions)
  • [main] 9 failures in step part-1 (3.9% fail rate in 230 executions)
  • [main] 2 failures in step release-tests (100.0% fail rate in 2 executions)
  • [main] 7 failures in pipeline elasticsearch-intake (6.5% fail rate in 108 executions)
  • [main] 10 failures in pipeline elasticsearch-pull-request (4.3% fail rate in 230 executions)

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

@elasticsearchmachine elasticsearchmachine added :Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. >test-failure Triaged test failures from CI labels Jan 10, 2025
elasticsearchmachine added a commit that referenced this issue Jan 10, 2025
…mpatibilityIT testSearchableSnapshotUpgrade {p0=[9.0.0, 9.0.0, 9.0.0]} #119990
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 consecutive failures in step release-tests
  • [main] 3 failures in test testSearchableSnapshotUpgrade {p0=[9.0.0, 9.0.0, 9.0.0]} (0.6% fail rate in 532 executions)
  • [main] 2 failures in step release-tests (100.0% fail rate in 2 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 Jan 10, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@henningandersen henningandersen added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 13, 2025
tlrx added a commit to tlrx/elasticsearch that referenced this issue Jan 14, 2025
Mixed cluster tests failed because a serialization change wasn't backported during a couple of days (elastic#119832).

Now the change is backported, we can reenable those tests.

Closes elastic#119990
Closes elastic#119989
Closes elastic#119980
Closes elastic#119979
Closes elastic#119978
@tlrx tlrx closed this as completed in e196138 Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. 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
Development

Successfully merging a pull request may close this issue.

2 participants