This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.3k
FSEventWrap: Aborting due to unwrap failure (Linux) #3997
Comments
Can you post a standalone test case? I get a lot of errors when I run
Or:
|
Sorry, I provided wrong install instructions. I've updated them, but still you can download standalone case from https://github.com/downloads/medikoo/node-ext/standalone-case-for-node-3997-bug.zip |
Thanks, I can reproduce the issue. |
ghost
assigned bnoordhuis
Sep 13, 2012
Fixed in db5c26e, thanks for the report. |
Great, Thank you! |
Hmm...this just happened to be in the middle of a big integration test I was running on node v0.9.12. I'll try to reproduce it in a smaller test case. Wanted to report it ASAP since I know v0.10 is about to come out. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Node v0.8.9 (observed also on v0.8.8, didn't check the others)
I can't narrow it down to simple test case, it's probably result of some race condition.
I have some test scripts that setup watchers (using
fs.watch
) and later change file system (removal, addition, update of files) in short periods of time. On Linux (Ubuntu 12.04) I get following error:It doesn't happen every time (about 7/10), but when it happens it happens as result of
fs.unlink
call on file that's being watched.Same error fails Travis tests: http://travis-ci.org/#!/medikoo/node-ext/jobs/2368332 (not sure what Linux distribution do Travis use).
You can reproduce it with:
The text was updated successfully, but these errors were encountered: