Uh oh!
There was an error while loading. Please reload this page.
Use NOCANCEL variants for close on Mac - #596
Conversation
Susurrus
commented
May 18, 2017
I'm seeing failures on Mac like |
alexcrichton
commented
May 18, 2017
Heh that's to be expected! It's ok to just add an exception for that as we're conciously expecting it to be different than the default |
The default on OS X does not provide clear errors, instead the NOCANCEL variants should be used. These are available as of OS X 10.6 onwards.
Susurrus
commented
May 19, 2017
docbrown
commented
May 19, 2017
@Susurrus I think you mean @DanielJoyce. :) |
Susurrus
commented
May 19, 2017
@docbrown Sorry, you're right! Too many PRs going around! |
alexcrichton
commented
May 19, 2017
@bors: r+ |
bors
commented
May 19, 2017
📌 Commit 9b9f36a has been approved by |
bors
commented
May 19, 2017
Use NOCANCEL variants for close on Mac The default `close()` on OS X does not provide clear errors, instead the `$NOCANCEL` variants should be used. These are available as of OS X 10.6 onwards. Fixes#595.
bors
commented
May 19, 2017
☀️ Test successful - status-appveyor, status-travis |
The default
close()on OS X does not provide clear errors, instead the$NOCANCELvariants should be used. These are available as of OS X 10.6 onwards.Fixes#595.