Skip to content

[CI] FileAccessTreeTests testDuplicatePrunedPaths failing #124006

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 Mar 4, 2025 · 3 comments · Fixed by #126717
Closed

[CI] FileAccessTreeTests testDuplicatePrunedPaths failing #124006

elasticsearchmachine opened this issue Mar 4, 2025 · 3 comments · Fixed by #126717
Assignees
Labels
:Core/Infra/Entitlements Entitlements infrastructure medium-risk An open issue or test failure that is a medium risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Mar 4, 2025

Build Scans:

Reproduction Line:

gradlew ":libs:entitlement:test" --tests "org.elasticsearch.entitlement.runtime.policy.FileAccessTreeTests.testDuplicatePrunedPaths" -Dtests.seed=10CF3219AE697D7F -Dtests.locale=dyo -Dtests.timezone=Etc/GMT-0 -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: expected:<[/a, /b/c, b/c/d, e/f]> but was:<[/a, /a/b, /b/c, b/c/d, e/f]>

Issue Reasons:

  • [main] 3 consecutive failures in step windows-2022_checkpart1_platform-support-windows
  • [main] 5 failures in test testDuplicatePrunedPaths (2.3% fail rate in 214 executions)
  • [main] 3 failures in step windows-2022_checkpart1_platform-support-windows (100.0% fail rate in 3 executions)
  • [main] 2 failures in step part-1-windows (66.7% fail rate in 3 executions)
  • [main] 3 failures in pipeline elasticsearch-periodic-platform-support (100.0% fail rate in 3 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.1% fail rate in 97 executions)

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

@elasticsearchmachine elasticsearchmachine added :Core/Infra/Entitlements Entitlements infrastructure >test-failure Triaged test failures from CI Team:Core/Infra Meta label for core/infra team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Mar 4, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 consecutive failures in step windows-2022_checkpart1_platform-support-windows
  • [main] 5 failures in test testDuplicatePrunedPaths (2.3% fail rate in 214 executions)
  • [main] 3 failures in step windows-2022_checkpart1_platform-support-windows (100.0% fail rate in 3 executions)
  • [main] 2 failures in step part-1-windows (66.7% fail rate in 3 executions)
  • [main] 3 failures in pipeline elasticsearch-periodic-platform-support (100.0% fail rate in 3 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (2.1% fail rate in 97 executions)

Build Scans:

dnhatn pushed a commit to dnhatn/elasticsearch that referenced this issue Mar 5, 2025
@ldematte ldematte added medium-risk An open issue or test failure that is a medium risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Mar 5, 2025
@ldematte
Copy link
Contributor

ldematte commented Mar 5, 2025

Patrick, I assigned this to you as you are working on a fix. Please remember to unmute the test too (it has been muted now)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Entitlements Entitlements infrastructure medium-risk An open issue or test failure that is a medium risk to future releases 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.

3 participants