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] FieldCapabilitiesIT testRelocation failing #119280

Closed
elasticsearchmachine opened this issue Dec 25, 2024 · 2 comments · Fixed by #121606
Closed

[CI] FieldCapabilitiesIT testRelocation failing #119280

elasticsearchmachine opened this issue Dec 25, 2024 · 2 comments · Fixed by #121606
Assignees
Labels
low-risk An open issue or test failure that is a low risk to future releases :StorageEngine/Mapping The storage related side of mappings Team:StorageEngine >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":server:internalClusterTest" --tests "org.elasticsearch.search.fieldcaps.FieldCapabilitiesIT.testRelocation" -Dtests.seed=86DAF5B842CFE490 -Dtests.locale=he-Hebr-IL -Dtests.timezone=Europe/Kaliningrad -Druntime.java=23

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: safeGet: listener was not completed within the timeout

Issue Reasons:

  • [8.x] 2 failures in test testRelocation (0.7% fail rate in 275 executions)

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

@elasticsearchmachine elasticsearchmachine added :StorageEngine/Mapping The storage related side of mappings >test-failure Triaged test failures from CI labels Dec 25, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.x

Mute Reasons:

  • [8.x] 2 failures in test testRelocation (0.7% fail rate in 275 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:StorageEngine needs:risk Requires assignment of a risk label (low, medium, blocker) labels Dec 25, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-storage-engine (Team:StorageEngine)

@dnhatn dnhatn self-assigned this Dec 27, 2024
@dnhatn dnhatn added the low-risk An open issue or test failure that is a low risk to future releases label Jan 15, 2025
@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Jan 15, 2025
dnhatn added a commit that referenced this issue Feb 4, 2025
The test failed because we tried to move a shard to a node that already 
has a copy. This change prevents that from happening.

Closes #119280
Closes #120772
dnhatn added a commit to dnhatn/elasticsearch that referenced this issue Feb 4, 2025
The test failed because we tried to move a shard to a node that already 
has a copy. This change prevents that from happening.

Closes elastic#119280
Closes elastic#120772
dnhatn added a commit to dnhatn/elasticsearch that referenced this issue Feb 4, 2025
The test failed because we tried to move a shard to a node that already
has a copy. This change prevents that from happening.

Closes elastic#119280
Closes elastic#120772
dnhatn added a commit to dnhatn/elasticsearch that referenced this issue Feb 4, 2025
The test failed because we tried to move a shard to a node that already
has a copy. This change prevents that from happening.

Closes elastic#119280
Closes elastic#120772
elasticsearchmachine pushed a commit that referenced this issue Feb 4, 2025
The test failed because we tried to move a shard to a node that already 
has a copy. This change prevents that from happening.

Closes #119280
Closes #120772
elasticsearchmachine pushed a commit that referenced this issue Feb 4, 2025
The test failed because we tried to move a shard to a node that already
has a copy. This change prevents that from happening.

Closes #119280
Closes #120772
elasticsearchmachine pushed a commit that referenced this issue Feb 4, 2025
The test failed because we tried to move a shard to a node that already
has a copy. This change prevents that from happening.

Closes #119280
Closes #120772
fzowl pushed a commit to voyage-ai/elasticsearch that referenced this issue Feb 4, 2025
The test failed because we tried to move a shard to a node that already 
has a copy. This change prevents that from happening.

Closes elastic#119280
Closes elastic#120772
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-risk An open issue or test failure that is a low risk to future releases :StorageEngine/Mapping The storage related side of mappings Team:StorageEngine >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants