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] SemanticInferenceMetadataFieldsRecoveryTests testSnapshotRecovery {p0=false p1=false} failing #124385

Open
elasticsearchmachine opened this issue Mar 7, 2025 · 4 comments
Labels
low-risk An open issue or test failure that is a low risk to future releases :SearchOrg/Relevance Label for the Search (solution/org) Relevance team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Mar 7, 2025

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:inference:test" --tests "org.elasticsearch.xpack.inference.mapper.SemanticInferenceMetadataFieldsRecoveryTests.testSnapshotRecovery {p0=false p1=true}" -Dtests.seed=B9603DA6C4BC43CD -Dtests.locale=kln-KE -Dtests.timezone=Etc/GMT+5 -Druntime.java=24

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Error when comparing xContent.
             _inference_fields: 
                      semantic_1: 
                         inference: 
                              chunks: 
                            semantic_1: 
                                       0: 
                                embeddings: 
                                           0: expected Double [0.061877843] but was Double [0.061877847]
                                           1: same [0.39140058]
                                           2: same [0.862135]
                                           3: same [0.20376408]
                                           4: same [0.26110643]
                                           5: same [0.41861713]
                                           6: same [0.26080924]
                                           7: same [0.019912839]
                                           8: same [0.9802829]
                                           9: expected 
[truncated]

Issue Reasons:

  • [8.x] 2 consecutive failures in test testSnapshotRecovery {p0=false p1=false}
  • [8.x] 2 consecutive failures in step rhel-9_platform-support-unix
  • [8.x] 2 consecutive failures in step rocky-9_platform-support-unix
  • [8.x] 18 failures in test testSnapshotRecovery {p0=false p1=false} (13.3% fail rate in 135 executions)
  • [8.x] 2 failures in step rhel-9_platform-support-unix (50.0% fail rate in 4 executions)
  • [8.x] 2 failures in step part-2 (14.3% fail rate in 14 executions)
  • [8.x] 2 failures in step rocky-9_platform-support-unix (66.7% fail rate in 3 executions)
  • [8.x] 3 failures in pipeline elasticsearch-periodic-platform-support (75.0% fail rate in 4 executions)
  • [8.x] 3 failures in pipeline elasticsearch-periodic (75.0% fail rate in 4 executions)
  • [8.x] 3 failures in pipeline elasticsearch-pull-request (25.0% fail rate in 12 executions)

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

@elasticsearchmachine elasticsearchmachine added :SearchOrg/Relevance Label for the Search (solution/org) Relevance team >test-failure Triaged test failures from CI labels Mar 7, 2025
elasticsearchmachine added a commit that referenced this issue Mar 7, 2025
…taFieldsRecoveryTests testSnapshotRecovery {p0=false p1=false} #124385
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 5 failures in test testSnapshotRecovery {p0=false p1=false} (0.6% fail rate in 780 executions)
  • [main] 4 failures in step part-2 (1.1% fail rate in 352 executions)
  • [main] 4 failures in pipeline elasticsearch-pull-request (1.1% fail rate in 351 executions)

Build Scans:

@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/search-eng (Team:SearchOrg)

@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/search-relevance (Team:Search - Relevance)

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.x

Mute Reasons:

  • [8.x] 2 consecutive failures in step rocky-9_platform-support-unix
  • [8.x] 13 failures in test testSnapshotRecovery {p0=false p1=false} (9.7% fail rate in 134 executions)
  • [8.x] 2 failures in step part-2 (13.3% fail rate in 15 executions)
  • [8.x] 2 failures in step rocky-9_platform-support-unix (66.7% fail rate in 3 executions)
  • [8.x] 3 failures in pipeline elasticsearch-periodic-platform-support (75.0% fail rate in 4 executions)
  • [8.x] 3 failures in pipeline elasticsearch-pull-request (23.1% fail rate in 13 executions)
  • [8.x] 2 failures in pipeline elasticsearch-periodic (66.7% fail rate in 3 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Mar 8, 2025
…taFieldsRecoveryTests testSnapshotRecovery {p0=false p1=false} #124385
@Mikep86 Mikep86 added the low-risk An open issue or test failure that is a low risk to future releases label Mar 10, 2025
georgewallace pushed a commit to georgewallace/elasticsearch that referenced this issue Mar 11, 2025
…taFieldsRecoveryTests testSnapshotRecovery {p0=false p1=false} elastic#124385
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 :SearchOrg/Relevance Label for the Search (solution/org) Relevance team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

2 participants