Trigger cleanup after failed test to avoid resource clashes #52
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.
This PR attempts to trigger immediate cleanup after any failed test so that the next tests do not conflict for left behind duplicate entries.
Two things are done:
postTestChecksis deferred immediately afterpreTestChecksinstead of keeping it at the end. This way it will be triggered even if the tests failpostTestCheckswill trigger leftover removal code in case the test is marked as failed and the leftover removal is not explicitly skippedt.Failed() && !skipLeftoversRemovalCaveat - if the test panics - it won't help, but panic is a hard error anyway
Example recovery cleanup: