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] CrossClusterQueryUnavailableRemotesIT testRemoteOnlyCCSAgainstDisconnectedRemoteWithSkipUnavailableTrue failing #121578

Closed
elasticsearchmachine opened this issue Feb 3, 2025 · 4 comments · Fixed by #121858
Assignees
Labels
:Analytics/ES|QL AKA ESQL needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:internalClusterTest" --tests "org.elasticsearch.xpack.esql.action.CrossClusterQueryUnavailableRemotesIT.testRemoteOnlyCCSAgainstDisconnectedRemoteWithSkipUnavailableTrue" -Dtests.seed=CD8B73F6EBD82287 -Dtests.locale=chr-Cher-US -Dtests.timezone=Europe/Sofia -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: <3>
     but: was <1>

Issue Reasons:

  • [main] 3 consecutive failures in test testRemoteOnlyCCSAgainstDisconnectedRemoteWithSkipUnavailableTrue
  • [main] 2 consecutive failures in step part-3
  • [main] 2 consecutive failures in pipeline elasticsearch-pull-request
  • [main] 3 failures in test testRemoteOnlyCCSAgainstDisconnectedRemoteWithSkipUnavailableTrue (1.7% fail rate in 178 executions)
  • [main] 2 failures in step part-3 (2.7% fail rate in 75 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.6% fail rate in 77 executions)

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

@elasticsearchmachine elasticsearchmachine added :Analytics/ES|QL AKA ESQL >test-failure Triaged test failures from CI labels Feb 3, 2025
elasticsearchmachine added a commit that referenced this issue Feb 3, 2025
…RemotesIT testRemoteOnlyCCSAgainstDisconnectedRemoteWithSkipUnavailableTrue #121578
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 consecutive failures in test testRemoteOnlyCCSAgainstDisconnectedRemoteWithSkipUnavailableTrue
  • [main] 2 consecutive failures in step part-3
  • [main] 2 consecutive failures in pipeline elasticsearch-pull-request
  • [main] 3 failures in test testRemoteOnlyCCSAgainstDisconnectedRemoteWithSkipUnavailableTrue (1.7% fail rate in 178 executions)
  • [main] 2 failures in step part-3 (2.7% fail rate in 75 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.6% fail rate in 77 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Feb 3, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-analytical-engine (Team:Analytics)

@elasticsearchmachine elasticsearchmachine added the needs:risk Requires assignment of a risk label (low, medium, blocker) label Feb 3, 2025
@smalyshev smalyshev self-assigned this Feb 4, 2025
@smalyshev
Copy link
Contributor

This should already be fixed but I'll double-check.

fzowl pushed a commit to voyage-ai/elasticsearch that referenced this issue Feb 4, 2025
…RemotesIT testRemoteOnlyCCSAgainstDisconnectedRemoteWithSkipUnavailableTrue elastic#121578
@smalyshev
Copy link
Contributor

This seems to point to old code, new code already has 1 in the test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/ES|QL AKA ESQL needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants