If all scenarios pass on retry, protractor still exits with status code 1

I am trying to debug an issue where I am using the new CucumberJS retry option yet the protractor process still returns an exit code of 1. My guess is that protractor-cucumber-framework reports the results to protractor which protractor then checks the failedCount and exists appropriately.

I don’t know the best spot to fix this - in protractor? In protractor-cucumber-framework?

One idea I had was that protractor-cucumber-framework would not report a failure to protractor if the retry worked, only if strict mode was false. Is this a valid option?

Right now, this is killing my ability to include this in my pipelines, as they evaluate the exit code. I would like my build to pass if everything works on retry.

[Phonesis]

I was never able to get it to work and ended up writing a script to handle the situation. It is annoying having to do it as adds a lot of overhead but works. It creates a txt file with a test/fail result logged for each test. At end of the run it will check if any txt file includes a fail status. If not, it will override exit code to ensure pipeline passes

[achuinard]

It just was merged, @AlexandrosD do we need a version bump / release?