Skip to content

[CI] CacheFileTests testCacheFileCreatedAsSparseFile failing #110801

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

Closed
elasticsearchmachine opened this issue Jul 11, 2024 · 4 comments · Fixed by #115582
Closed

[CI] CacheFileTests testCacheFileCreatedAsSparseFile failing #110801

elasticsearchmachine opened this issue Jul 11, 2024 · 4 comments · Fixed by #115582
Assignees
Labels
:Core/Infra/Core Core issues without another label needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:searchable-snapshots:test" --tests "org.elasticsearch.xpack.searchablesnapshots.cache.common.CacheFileTests.testCacheFileCreatedAsSparseFile" -Dtests.seed=28FF9A4D7FBE85EB -Dtests.locale=hu-HU -Dtests.timezone=Asia/Choibalsan -Druntime.java=17

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.UnsatisfiedLinkError: Error looking up function 'fstat64': /opt/buildkite-agent/.java/graalvm-ce17/bin/java: undefined symbol: fstat64

Issue Reasons:

  • [main] 3 consecutive failures in test testCacheFileCreatedAsSparseFile
  • [main] 8 failures in test testCacheFileCreatedAsSparseFile (2.4% fail rate in 334 executions)
  • [main] 5 failures in step part-2 (4.0% fail rate in 125 executions)
  • [main] 5 failures in pipeline elasticsearch-pull-request (4.0% fail rate in 125 executions)

Note:
This issue was created using new, in-development muting automation. Please mind any issues.

@elasticsearchmachine elasticsearchmachine added :Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI labels Jul 11, 2024
elasticsearchmachine added a commit that referenced this issue Jul 11, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 consecutive failures in test testCacheFileCreatedAsSparseFile
  • [main] 8 failures in test testCacheFileCreatedAsSparseFile (2.4% fail rate in 334 executions)
  • [main] 5 failures in step part-2 (4.0% fail rate in 125 executions)
  • [main] 5 failures in pipeline elasticsearch-pull-request (4.0% fail rate in 125 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Core/Infra Meta label for core/infra team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jul 11, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-core-infra (Team:Core/Infra)

@rjernst
Copy link
Member

rjernst commented Jul 13, 2024

Should be fixed by #110807

@elasticsearchmachine
Copy link
Collaborator Author

This issue is being re-opened because the referenced test still exists in muted-tests.yml, so it is still muted.

Please check and unmute the test if it can be unmuted.

In the future, automation will automatically re-open issues whenever they are closed without unmuting the test first.

Reach out in #es-delivery or tag the delivery team if you have an issue.

cc @rjernst

rjernst added a commit to rjernst/elasticsearch that referenced this issue Oct 24, 2024
The test issue was fixed by elastic#110807

closes elastic#110801
@rjernst rjernst removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Oct 24, 2024
@elasticsearchmachine elasticsearchmachine added the needs:risk Requires assignment of a risk label (low, medium, blocker) label Oct 24, 2024
georgewallace pushed a commit to georgewallace/elasticsearch that referenced this issue Oct 25, 2024
jfreden pushed a commit to jfreden/elasticsearch that referenced this issue Nov 4, 2024
tvernum pushed a commit that referenced this issue Feb 25, 2025
tvernum pushed a commit that referenced this issue Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants