-
Notifications
You must be signed in to change notification settings - Fork 25k
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 org.elasticsearch.xpack.security.authz.ReadActionsTests testEmptyAuthorizedIndicesSearchForWildcard fails #30098
Labels
:Security/Security
Security issues without another label
>test-failure
Triaged test failures from CI
Comments
Original comment by @jaymode: @albertzaharovits can you take a look at this failure? |
Original comment by @albertzaharovits: Will do! It does not reproduce locally either. |
Original comment by @tlrx: Different test in the same class with a similar error on 6.x:
It does not reproduce for me locally. Failed job is REDACTED LINK |
elasticmachine
added
:Security/Security
Security issues without another label
>test-failure
Triaged test failures from CI
labels
Apr 25, 2018
recent build failure: Reproduce steps
|
colings86
added a commit
that referenced
this issue
Aug 31, 2018
) * Fixes SecurityIntegTestCase so it always adds at least one alias `SecurityIntegTestCase.createIndicesWithRandomAliases` could randomly fail because its not gauranteed that the randomness of which aliases to add to the `IndicesAliasesRequestBuilder` would always select at least one alias to add. This change fixes the problem by keeping track of whether we have added an alias to teh request and forcing the last alias to be added if no other aliases have been added so far. Closes #30098 Closes #33123e * Addresses review comments
colings86
added a commit
that referenced
this issue
Aug 31, 2018
(#33296) * Fixes SecurityIntegTestCase so it always adds at least one alias `SecurityIntegTestCase.createIndicesWithRandomAliases` could randomly fail because its not gauranteed that the randomness of which aliases to add to the `IndicesAliasesRequestBuilder` would always select at least one alias to add. This change fixes the problem by keeping track of whether we have added an alias to teh request and forcing the last alias to be added if no other aliases have been added so far. Closes #30098 Closes #33123e * Addresses review comments
colings86
added a commit
that referenced
this issue
Aug 31, 2018
(#33296) * Fixes SecurityIntegTestCase so it always adds at least one alias `SecurityIntegTestCase.createIndicesWithRandomAliases` could randomly fail because its not gauranteed that the randomness of which aliases to add to the `IndicesAliasesRequestBuilder` would always select at least one alias to add. This change fixes the problem by keeping track of whether we have added an alias to teh request and forcing the last alias to be added if no other aliases have been added so far. Closes #30098 Closes #33123e * Addresses review comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Security/Security
Security issues without another label
>test-failure
Triaged test failures from CI
Original comment by @nik9000:
This ReadActionsTests failure doesn't reproduce for me locally.
The text was updated successfully, but these errors were encountered: