-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
This reverts commit 29b7c5c.
- Loading branch information
Showing
3 changed files
with
36 additions
and
21 deletions.
There are no files selected for viewing
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
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
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
7d4ae60
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.
@halter73 no manual reset events
7d4ae60
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 set
Scheduler = PipeScheduler.Inline
in the test ctor as part of this change to ensure both WaitHandles are already be completed by the time WaitOne is called.This is verifying the CTS backing RequestAborted token (if there is one) isn't disposed. For a second, we could just verify CancellationTokenRegistration.Token getter didn't throw an ODE, but that's been fixed.
Would you prefer I make the WaitOne timeout 0? Or just call the WaitHandle getter? I'm pretty sure it's the getter that would throw the ODE, not the call to WaitOne anyway. I don't think it's a big deal how we do it since it's already completed.