If the finish task is called with exit code 143 witch coresponds to SIGT...#43
Open
nistormihai wants to merge 2 commits intoericclemmons:masterfrom
nistormihai:master
Open
If the finish task is called with exit code 143 witch coresponds to SIGT...#43nistormihai wants to merge 2 commits intoericclemmons:masterfrom nistormihai:master
nistormihai wants to merge 2 commits intoericclemmons:masterfrom
nistormihai:master
Conversation
Owner
|
@paulpflug What do you think? Good to merge this down? |
Collaborator
|
@ericclemmons I think this problem should be fixed with version 4.1.19 already |
Collaborator
|
Still not sure if this is a good idea. A decision better left to @paulpflug and @ericclemmons. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've tried to work with grunt-express-server here: https://github.com/nistormihai/grunt-express-server-test
on ubuntu precise 64
with livereload for node rendering but it seemed that the livereload was reloading the browser
before the express server started.
I found out that somehow the finish process was triggered by grunt.util.spawn with the exiting task,
and with the exit code 143 see here: http://stackoverflow.com/questions/4192364/always-app-java-end-with-exit-143-ubuntu
So my fix was just to exit if code 143 was received.
Maybe is not the best approach but I didn't had more time to investigate this thoroughly.