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.

Sign up for GitHub

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

Jump to bottom

[CI] CoreWithSecurityClientYamlTestSuiteIT test {yaml=update/100_synthetic_source/keyword} failing #122101

Closed
elasticsearchmachine opened this issue Feb 7, 2025 · 3 comments · Fixed by #122154
Closed

[CI] CoreWithSecurityClientYamlTestSuiteIT test {yaml=update/100_synthetic_source/keyword} failing #122101

elasticsearchmachine opened this issue Feb 7, 2025 · 3 comments · Fixed by #122154
Assignees
@kkrik-es
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 ":x-pack:qa:core-rest-tests-with-security:yamlRestTest" --tests "org.elasticsearch.xpack.security.CoreWithSecurityClientYamlTestSuiteIT.test {yaml=update/100_synthetic_source/stored text}" -Dtests.seed=78EA00D2F5CB779A -Dbuild.snapshot=false -Dtests.jvm.argline="-Dbuild.snapshot=false" -Dlicense.key=x-pack/license-tools/src/test/resources/public.key -Dtests.locale=tr-Latn-TR -Dtests.timezone=Asia/Hovd -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [update/100_synthetic_source:126]: field [test.fields._recovery_source] should be null but was [{total=110b, total_in_bytes=110, inverted_index={total=0b, total_in_bytes=0}, stored_fields=110b, stored_fields_in_bytes=110, doc_values=0b, doc_values_in_bytes=0, points=0b, points_in_bytes=0, norms=0b, norms_in_bytes=0, term_vectors=0b, term_vectors_in_bytes=0, knn_vectors=0b, knn_vectors_in_bytes=0}] expected null, but was:<{total=110b, total_in_bytes=110, inverted_index={total=0b, total_in_bytes=0}, stored_fields=110b, stored_fields_in_bytes=110, doc_values=0b, doc_values_in_bytes=0, points=0b, points_in_bytes=0, norms=0b, norms_in_bytes=0, term_vectors=0b, term_vectors_in_bytes=0, knn_vectors=0b, knn_vectors_in_bytes=0}>

Issue Reasons:

  • [main] 9 failures in test test {yaml=update/100_synthetic_source/keyword} (1.4% fail rate in 653 executions)
  • [main] 5 failures in step checkpart4_release-tests (71.4% fail rate in 7 executions)
  • [main] 2 failures in step part-4-entitlements (11.8% fail rate in 17 executions)
  • [main] 8 failures in pipeline elasticsearch-pull-request (3.0% fail rate in 268 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Data Management/Data streams Data streams and their lifecycles >test-failure Triaged test failures from CI labels Feb 7, 2025
elasticsearchmachine added a commit that referenced this issue Feb 7, 2025
@elasticsearchmachine
Mute org.elasticsearch.xpack.security.CoreWithSecurityClientYamlTestS…
80916dd 
…uiteIT test {yaml=update/100_synthetic_source/keyword} #122101
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 9 failures in test test {yaml=update/100_synthetic_source/keyword} (1.4% fail rate in 653 executions)
  • [main] 5 failures in step checkpart4_release-tests (71.4% fail rate in 7 executions)
  • [main] 2 failures in step part-4-entitlements (11.8% fail rate in 17 executions)
  • [main] 8 failures in pipeline elasticsearch-pull-request (3.0% fail rate in 268 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 7, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-data-management (Team:Data Management)

@dnhatn dnhatn added :StorageEngine/Mapping The storage related side of mappings and removed :Data Management/Data streams Data streams and their lifecycles labels Feb 8, 2025
@dnhatn dnhatn self-assigned this Feb 8, 2025
@dnhatn dnhatn 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 Feb 8, 2025
@elasticsearchmachine elasticsearchmachine added Team:StorageEngine and removed Team:Data Management Meta label for data/management team labels Feb 8, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@kkrik-es kkrik-es mentioned this issue Feb 10, 2025
Merged
@kkrik-es kkrik-es assigned kkrik-es and unassigned dnhatn Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kkrik-es kkrik-es

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
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[TEST] Unmute CoreWithSecurityClientYamlTestSuiteIT tests kkrik-es/elasticsearch
3 participants
@dnhatn @elasticsearchmachine @kkrik-es