Skip to content

[CI] PolicyManagerTests testFilesEntitlementsWithExclusive failing #124420

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 8, 2025 · 6 comments
Closed
Labels
:Core/Infra/Entitlements Entitlements infrastructure low-risk An open issue or test failure that is a low 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 8, 2025

Build Scans:

Reproduction Line:

gradlew ":libs:entitlement:test" --tests "org.elasticsearch.entitlement.runtime.policy.PolicyManagerTests.testFilesEntitlementsWithExclusive" -Dtests.seed=D4500143087F811E -Dtests.locale=nb-SJ -Dtests.timezone=Asia/Macau -Druntime.java=24

Applicable branches:
9.0

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: (a string containing "Path [/base/test] is already exclusive" and a string containing "[plugin1][test.module1]" and a string containing "[plugin2][test.module2]" and a string containing "cannot add exclusive access")
     but: a string containing "Path [/base/test] is already exclusive" was "Path [C:\base\test] is already exclusive to [plugin1][test.module1], cannot add exclusive access for [plugin2][test.module2]"

Issue Reasons:

  • [9.0] 9 consecutive failures in step windows-2022_checkpart1_platform-support-windows
  • [9.0] 12 failures in test testFilesEntitlementsWithExclusive (2.5% fail rate in 482 executions)
  • [9.0] 9 failures in step windows-2022_checkpart1_platform-support-windows (56.3% fail rate in 16 executions)
  • [9.0] 3 failures in step part-1 (5.4% fail rate in 56 executions)
  • [9.0] 8 failures in pipeline elasticsearch-periodic-platform-support (50.0% fail rate in 16 executions)
  • [9.0] 3 failures in pipeline elasticsearch-pull-request (5.5% fail rate in 55 executions)

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

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

This has been muted on branch main

Mute Reasons:

  • [main] 5 failures in test testFilesEntitlementsWithExclusive (0.6% fail rate in 778 executions)
  • [main] 4 failures in step part-1 (1.2% fail rate in 331 executions)
  • [main] 4 failures in pipeline elasticsearch-pull-request (1.2% fail rate in 328 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 Mar 8, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@ldematte ldematte added the low-risk An open issue or test failure that is a low risk to future releases label Mar 9, 2025
@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Mar 9, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.18

Mute Reasons:

  • [8.18] 3 failures in test testFilesEntitlementsWithExclusive (2.3% fail rate in 129 executions)
  • [8.18] 2 failures in step part-1 (16.7% fail rate in 12 executions)
  • [8.18] 2 failures in pipeline elasticsearch-pull-request (18.2% fail rate in 11 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Mar 10, 2025
georgewallace pushed a commit to georgewallace/elasticsearch that referenced this issue Mar 11, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.x

Mute Reasons:

  • [8.x] 4 consecutive failures in step windows-2019_checkpart1_platform-support-windows
  • [8.x] 3 consecutive failures in step windows-2022_checkpart1_platform-support-windows
  • [8.x] 8 failures in test testFilesEntitlementsWithExclusive (4.3% fail rate in 186 executions)
  • [8.x] 4 failures in step windows-2019_checkpart1_platform-support-windows (80.0% fail rate in 5 executions)
  • [8.x] 3 failures in step windows-2022_checkpart1_platform-support-windows (75.0% fail rate in 4 executions)
  • [8.x] 4 failures in pipeline elasticsearch-periodic-platform-support (80.0% fail rate in 5 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Mar 11, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 9.0

Mute Reasons:

  • [9.0] 9 consecutive failures in step windows-2022_checkpart1_platform-support-windows
  • [9.0] 12 failures in test testFilesEntitlementsWithExclusive (2.5% fail rate in 482 executions)
  • [9.0] 9 failures in step windows-2022_checkpart1_platform-support-windows (56.3% fail rate in 16 executions)
  • [9.0] 3 failures in step part-1 (5.4% fail rate in 56 executions)
  • [9.0] 8 failures in pipeline elasticsearch-periodic-platform-support (50.0% fail rate in 16 executions)
  • [9.0] 3 failures in pipeline elasticsearch-pull-request (5.5% fail rate in 55 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Mar 13, 2025
@ldematte ldematte added :Core/Infra/Entitlements Entitlements infrastructure and removed :Core/Infra/Core Core issues without another label labels Mar 13, 2025
@prdoyle
Copy link
Contributor

prdoyle commented May 2, 2025

Already fixed.

@prdoyle prdoyle closed this as completed May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Entitlements Entitlements infrastructure low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

3 participants