Fix FiberAsyncTest.whenCancelRunBlockingInterruptExecutingThread() #267
Conversation
This file contains 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
added 2 commits
May 2, 2017 10:53
…uptExecutingThread().
… for the time being.
felixvf
force-pushed
the
fix_FiberAsyncTest
branch
from
bd9f85b
to
8aef9a5
Compare
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 change makes the test of FiberAsyncTest.whenCancelRunBlockingInterruptExecutingThread() be run repeatedly in order to increase the failure chance of this test. With that change, the test fails with a much higher probability. This allows bug #266 to be analyzed.
In order to still allow further development while this bug is not fixed, this test is tagged as
@Ignoreuntil the underlying cause is fixed.