Closed tandrewnichols closed 9 years ago
Hey Andrew sorry nobody has replied to you here but this is a passion of @davemo's and he might be interested to think about the ramifications of server restarts on watch when/if the server is complex.
Hi @tandrewnichols, is this still a problem for you or did you manage to find a solution?
Yeah, we found a solution, although we don't use lineman anymore, so I don't recall what it was.
Seems like every time we save a file being watched and our server restarts, we get this in the spawn output (Note the "error" reported by "watch" the second time):
This isn't a problem most of the time. But we've noticed that sometimes (and who knows why), this same error/code (143) is reported when travis runs . . . which it interprets as a test failure, even if all the tests actually passed.
We're not using the most recent lineman, but I pulled down the most recent and verified that it still happens there. This may be a lineman issue, or it may just be an issue with our server task, though I don't see anything specifically wrong with the task, and a similar task (and I mean, nearly identical) that I run in another project, but directly with grunt, doesn't have this problem.
Any insight?