it looks like there is a data race to fix

it looks like there is a data race to fix

#150

Still seeing data races on Travis. Doh!

Specifically on macOS. The race on Linux is resolved.

the data race is in the bsd build; that uses kqueue instead of inotify. #177 will not help here

data races in all the places

will come back to that one. 💤

on macOS Sierra 10.12

❯ go test -race -test.count=10
PASS
ok      github.com/fsnotify/fsnotify    104.165s

fsnotify git/master  
❯ go16 test -race -test.count=10

... the later doesn't seem to be finishing anytime soon

❯ go16 test -race 
# testmain
fatal error: unexpected signal during runtime execution
...

But then Go 1.6 doesn't work on Sierra anyway. I wonder what version of macOS Travis is running? Might need a macOS VM just to test Go 1.6 locally. 😢

well this is embarrassing... 😊

updated for Go 1.8

also requested Go 1.8 for AppVeyor. appveyor/ci#1330

Currently Windows tests are using Go 1.7.1

FWIW you can use 1.x to get the latest stable release of Go, and (for example) 1.7.x to get the latest version of 1.7. For example:

go:
  - 1.7.x
  - 1.x
  - tip

@twpayne Thanks for the note. The only problem with using .x is we need to wait for Travis CI to update their aliases, but they are in place now. I will update.

See: travis-ci/travis-build#956