-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Unblock blocked repositories after test execution #61703
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
fcofdez
wants to merge
13
commits into
elastic:main
from
fcofdez:unblock-blocked-repositories-after-test
Closed
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
8010e3b
Unblock blocked repositories after test execution.
fcofdez 5e7e95b
Check for repository instance type
fcofdez bdfc369
Move repository unblock to ESIntegTestCase cluster cleanup
fcofdez fad2cf8
Don't unblock repositories on non internal clusters
fcofdez cba3bcd
Unblock repositories only when the cluster is open
fcofdez 388d261
Merge remote-tracking branch 'origin/master' into unblock-blocked-rep…
fcofdez 7207a56
Merge remote-tracking branch 'origin/master' into unblock-blocked-rep…
fcofdez 60db1e3
Rename awaitNoMoreRunningSnapshotOperations
fcofdez 9aee157
Merge remote-tracking branch 'origin/master' into unblock-blocked-rep…
fcofdez 3b3cf8f
Keep track of blocked repos on AbstractSnapshotIntegTestCase.
fcofdez 0d7a454
Merge remote-tracking branch 'origin/master' into unblock-blocked-rep…
fcofdez 2849021
Use a Set instead
fcofdez f858059
fix checkstyle
fcofdez File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I like the idea of this, but I'm a little suspicious that this is the right place to put this. Many tests don't reuse the test cluster in which case the work here is unnecessary? Maybe we should make this change in the logic that cleans up the test cluster when its reused instead?
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.
The problem is that
@After
hooks fromAbstractSnapshotIntgetTestCase
are executed before the hooks inESIntegTestCase
. Is there a way to determine the scope of a cluster? we could bypass this cleanup if the cluster is not reused?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.
Maybe we can do a simpler thing and simply skip the repo consistency checks in case of test failure via wrapping in:
That should fix all the cases because I think closing the repos upstream in the
EsIntegTestCase
cleanup logic should deal with unblocking and removing all the repos cleanly.That would also make test failures easier to interpret since we get rid of failed repo verifications on failed tests?