Test that the interrupted InterruptibleTask does in fact produce InterruptedException.
#7792
+42
−18
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.
Test that the interrupted
InterruptibleTaskdoes in fact produceInterruptedException.I added this as part of debugging an inexplicable flaky failure under Android Lollipop. The failure remains inexplicable, but I figured I might as well submit the new assertion.
This assertion, by blocking on some
InterruptibleTaskoutput, conveniently makes the existing blocking injoinobsolete.RELNOTES=n/a