failed test: test-fs-watch.js on freebsd10.2

[jbergstroem]

Seems to timeout.

Also, the regression looks recent: https://ci.nodejs.org/computer/iojs-digitalocean-freebsd102-64-2/builds

[Trott]

Everything starting at line 130 was added in 87e820e. I propose moving that content to its own file, as it is essentially an independent test. Then we can watch subsequent CI tests and see if it fails in that bit of code or in the previously existing code.

[Fishrock123]

Any update on this? has it continued after split up?

[Trott]

After the split up, neither test has failed. Which is weird because one of them should have continued failing. So maybe it's some oddball filesystem interaction between the two tests that only manifests on FreeBSD? Or maybe there's been some change in the FreeBSD build that fixed things? I don't know.

I'm comfortable closing this unless/until some issue starts to manifest itself again. And I'm comfortable leaving it open as a marker that something strange and unexplained is going on. Either way...

[jbergstroem]

This is a new slave in CI which is why I was a bit more trigger happy to report it (hoping for increased visibility). Happy to close and reopen if necessary.