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] ProfileIntegTests testSuggestProfilesWithHint failing #121116

Open
elasticsearchmachine opened this issue Jan 28, 2025 · 4 comments · May be fixed by #121466
Open

[CI] ProfileIntegTests testSuggestProfilesWithHint failing #121116

elasticsearchmachine opened this issue Jan 28, 2025 · 4 comments · May be fixed by #121466
Assignees
Labels
low-risk An open issue or test failure that is a low risk to future releases :Security/Security Security issues without another label Team:Security Meta label for security team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Jan 28, 2025

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:security:internalClusterTest" --tests "org.elasticsearch.xpack.security.profile.ProfileIntegTests.testSuggestProfilesWithHint" -Dtests.seed=5126C1569F5376DD -Dtests.locale=hi -Dtests.timezone=America/Rainy_River -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: safeGet: listener was completed exceptionally

Issue Reasons:

  • [main] 12 failures in test testSuggestProfilesWithHint (1.3% fail rate in 955 executions)
  • [main] 5 failures in step part4 (2.9% fail rate in 172 executions)
  • [main] 6 failures in step part-4 (1.5% fail rate in 393 executions)
  • [main] 5 failures in pipeline elasticsearch-intake (2.9% fail rate in 172 executions)
  • [main] 6 failures in pipeline elasticsearch-pull-request (1.6% fail rate in 381 executions)

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

@elasticsearchmachine elasticsearchmachine added :Security/Security Security issues without another label >test-failure Triaged test failures from CI labels Jan 28, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.x

Mute Reasons:

  • [8.x] 2 failures in test testSuggestProfilesWithHint (1.2% fail rate in 173 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Security Meta label for security team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 28, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-security (Team:Security)

@slobodanadamovic slobodanadamovic self-assigned this Jan 29, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 9.0

Mute Reasons:

  • [9.0] 2 failures in test testSuggestProfilesWithHint (4.8% fail rate in 42 executions)

Build Scans:

@slobodanadamovic slobodanadamovic 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 Jan 31, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 11 failures in test testSuggestProfilesWithHint (1.2% fail rate in 936 executions)
  • [main] 5 failures in step part4 (2.9% fail rate in 170 executions)
  • [main] 6 failures in step part-4 (1.5% fail rate in 393 executions)
  • [main] 5 failures in pipeline elasticsearch-intake (2.9% fail rate in 170 executions)
  • [main] 6 failures in pipeline elasticsearch-pull-request (1.6% fail rate in 381 executions)

Build Scans:

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 :Security/Security Security issues without another label Team:Security Meta label for security team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants