-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Ensure the cleanup in testAutoFollowPatterns is always happening #85401
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
Conversation
In case of failure testAutoFollowPatterns will leave autofollowing pattern ranning that would case assertion failure in other test cases
|
Pinging @elastic/es-distributed (Team:Distributed) |
| } finally { | ||
| // Cleanup by deleting auto follow pattern and pause following: | ||
| assertOK(client().performRequest(new Request("DELETE", "/_ccr/auto_follow/test_pattern"))); | ||
| pauseFollow(client(), allowedIndex); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actual fix
tlrx
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
.../plugin/ccr/qa/security/src/test/java/org/elasticsearch/xpack/ccr/FollowIndexSecurityIT.java
Outdated
Show resolved
Hide resolved
.../plugin/ccr/qa/security/src/test/java/org/elasticsearch/xpack/ccr/FollowIndexSecurityIT.java
Outdated
Show resolved
Hide resolved
|
Thank you, @tlrx! |
|
@elasticmachine please run elasticsearch-ci/part-1 |
💔 Backport failed
You can use sqren/backport to manually backport by running |
) In case of failure testAutoFollowPatterns will leave auto-following pattern running that would case assertion failure in other test cases (cherry picked from commit 92c4538)
…stic#85401) In case of failure testAutoFollowPatterns will leave auto-following pattern running that would case assertion failure in other test cases (cherry picked from commit 92c4538)
#85481) * Assert actual follow tasks instead of count (#85151) Currently, the test is flaky and sometimes fails with expected 1 but was 2 failure. Updating the code to assert against collection content to collect additional information on the cause of the failure. (cherry picked from commit e31be1b) * Ensure the cleanup in testAutoFollowPatterns is always happening (#85401) In case of failure testAutoFollowPatterns will leave auto-following pattern running that would case assertion failure in other test cases (cherry picked from commit 92c4538)
…ng (#85482) * Assert actual follow tasks instead of count (#85151) Currently, the test is flaky and sometimes fails with expected 1 but was 2 failure. Updating the code to assert against collection content to collect additional information on the cause of the failure. (cherry picked from commit e31be1b) * Ensure the cleanup in testAutoFollowPatterns is always happening (#85401) In case of failure testAutoFollowPatterns will leave auto-following pattern running that would case assertion failure in other test cases (cherry picked from commit 92c4538) * revert java 17 usage
In case of failure testAutoFollowPatterns will leave autofollowing
pattern running that would case assertion failure in other test cases
Closes: #85147