Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding test for failure in kqueue close #145

Closed
wants to merge 1 commit into from
Closed

Adding test for failure in kqueue close #145

wants to merge 1 commit into from

Conversation

nikunjy
Copy link

@nikunjy nikunjy commented May 20, 2016

Run the test on a mac
go test -run TestWatcherClose -count 5

@nathany
Copy link
Contributor

nathany commented Jun 28, 2016

Thanks for providing a failing test. I won't be merging it until we have a fix, nor will I be merging in with an additional testing dependency (as good as testify may be).

@nikunjy
Copy link
Author

nikunjy commented Jun 28, 2016

@nathany fair enough. I slacked off on making the fix. Will bounce back with the fix and do the test without testify.

@nathany
Copy link
Contributor

nathany commented Jun 28, 2016

Thanks. Would you mind also taking a peek at #124?

@nathany nathany closed this in 3d33f50 Jan 10, 2018
aaronbee pushed a commit to aristanetworks/fsnotify that referenced this pull request Dec 26, 2019
* avoid deadlocks on Close()

raw channel work (not inside a select) should
always be prohibited in production code, as
it readily causes deadlocks on shutdown.

Also adds the test TestWatcherClose from fsnotify#145.
This request duplicates that test, with two
lines fixed to address the houndcli-bot review
concerns.

Fixes fsnotify#187
Fixes fsnotify#145

* cleanup and simpler test

* also fix fsnotify#225

* fix tests

Cherry-pick of
fsnotify@3d33f50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants