Fix flaky test attribute not working #6253
Merged
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's a few issues here:
AssertionException
s. The latter are handled specially by NUnit to allow retries.[TearDown]
, it does not re-run the test at all.Using
TestActionAttribute
allows us to do basically the same thing without running into the second issue. Note however that this does not do anything like trying to recover theGameHost
after a non-assertion exception, so those will still fail immediately and not retry. I think that this is fine and "intentional".Until steps now throw an
AssertionException
instead of aTimeoutException
. I don't believe we rely on this anywhere. Messaging has also changed a bit:I've run a full osu! test run with this without issue.