Grunt return 0 even if a protractorjs test fail

[jarl-dk]

According to gruntjs/grunt#1114
It is a problem in grunt-protractor-runner

I see

Running "protractor:run" (protractor) task
Using the selenium server at http://localhost:4444/wd/hub
[launcher] Running 1 instances of WebDriver[launcher] chrome passed
>> 
>> Test failed but keep the grunt process alive.

Done, without errors.

Can you confirm it is a problem in this project?

[Brootux]

I think the problem is this

>> Test failed but keep the grunt process alive.

Do you setup keepAlive: true anywhere in your grunt and/or protractor configuration?

[jarl-dk]

Yes, my Gruntfile.js contains a keepAlive: true. If I commentthat out it seems to behave as expected. I also checked that the return code was 1 if I run protractor without grunt, like
node node_modules/protractor/bin/protractor protractor.conf.js --verbose, in this case it also returned 1. So I guess everything is as it should be in protractor... Sorry for any inconvenience.

[AndersDJohnson]

I still have a need to run other grunt tasks after a failed test - e.g. to shutdown my local server and disconnect from Sauce Connect. Does Grunt have an API for deferring failed exit status codes? gruntjs/grunt#1114