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 testMountSearchableSnapshot {p0=[9.0.0, 8.18.0, 8.18.0]} failing #119550

Open
elasticsearchmachine opened this issue Jan 4, 2025 · 3 comments
Assignees
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 4, 2025

Build Scans:

Reproduction Line:

./gradlew ":qa:lucene-index-compatibility:javaRestTest" --tests "org.elasticsearch.lucene.RollingUpgradeSearchableSnapshotIndexCompatibilityIT" -Dtests.method="testMountSearchableSnapshot {p0=[9.0.0, 8.18.0, 8.18.0]}" -Dtests.seed=82B30E3DBCBE7C81 -Dtests.locale=es-GQ -Dtests.timezone=Asia/Dushanbe -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] 7 consecutive failures in test testMountSearchableSnapshot {p0=[9.0.0, 8.18.0, 8.18.0]}
  • [main] 3 consecutive failures in step part1
  • [main] 5 consecutive failures in step part-1
  • [main] 3 consecutive failures in step release-tests
  • [main] 3 consecutive failures in pipeline elasticsearch-intake
  • [main] 5 consecutive failures in pipeline elasticsearch-pull-request
  • [main] 14 failures in test testMountSearchableSnapshot {p0=[9.0.0, 8.18.0, 8.18.0]} (2.5% fail rate in 563 executions)
  • [main] 3 failures in step part1 (2.9% fail rate in 104 executions)
  • [main] 8 failures in step part-1 (3.5% fail rate in 231 executions)
  • [main] 3 failures in step release-tests (100.0% fail rate in 3 executions)
  • [main] 3 failures in pipeline elasticsearch-intake (2.9% fail rate in 104 executions)
  • [main] 9 failures in pipeline elasticsearch-pull-request (3.9% fail rate in 230 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic (22.2% fail rate in 9 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 4, 2025
elasticsearchmachine added a commit that referenced this issue Jan 4, 2025
…mpatibilityIT testMountSearchableSnapshot {p0=[9.0.0, 8.18.0, 8.18.0]} #119550
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 consecutive failures in step release-tests
  • [main] 3 failures in test testMountSearchableSnapshot {p0=[9.0.0, 8.18.0, 8.18.0]} (4.8% fail rate in 63 executions)
  • [main] 3 failures in step release-tests (100.0% fail rate in 3 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic (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 4, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@tlrx tlrx 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 6, 2025
@tlrx tlrx self-assigned this Jan 7, 2025
elasticsearchmachine pushed a commit that referenced this issue Jan 8, 2025
The tests added in #119468 do not work when executed in the
`release-test` pipeline: at some point a 9.0 non-snapshot node tries to
join the 8.18.0-SNAPSHOT cluster which is impossible due to a missing
`esql.metrics_syntax` feature which is only declared in snapshot builds.

Additionaly, the tests rely on unrelease code in 8.x so they won't work
until 8.18.0 is released.

I don't know how we deal with such issues today, but I'd like to unmute
the tests so that they are executed on CI while being disabled in
`release-test`.

Releates #119550
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 consecutive failures in test testMountSearchableSnapshot {p0=[9.0.0, 8.18.0, 8.18.0]}
  • [main] 2 consecutive failures in step part-1
  • [main] 3 consecutive failures in step release-tests
  • [main] 2 consecutive failures in pipeline elasticsearch-pull-request
  • [main] 9 failures in test testMountSearchableSnapshot {p0=[9.0.0, 8.18.0, 8.18.0]} (1.6% fail rate in 558 executions)
  • [main] 5 failures in step part-1 (2.2% fail rate in 228 executions)
  • [main] 3 failures in step release-tests (100.0% fail rate in 3 executions)
  • [main] 6 failures in pipeline elasticsearch-pull-request (2.6% fail rate in 227 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic (22.2% fail rate in 9 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Jan 10, 2025
…mpatibilityIT testMountSearchableSnapshot {p0=[9.0.0, 8.18.0, 8.18.0]} #119550
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

No branches or pull requests

2 participants