travis: continue static tests on error

[cgundogan]

Continue static tests even if one of them fails. This way we might get more feedback in one run, instead of having a running - testing - running - testing loop.

In the current implementation the script exits as soon as one of static tests fail (because of set -e).

[OlegHahm]

Not sure - @authmillenon, what do you think?

[cgundogan]

what's the benefit of not running cppcheck if the doxycheck failed beforehand? (:

[OlegHahm]

Time.

[cgundogan]

I disagree. IMO, it is much more time efficient to run them all in one slide instead of waiting for travis to enqueue the job again.

[miri64]

Actually this is how this script is supposed to work. I do not know why the old solution did not work out (though I tried to debug multiple times). We don't save time if Travis is nitpicking over each time about a different thing and it's frustrating for new contributors. Just one question: what if the result is neither one nor zero? Is this also catched?

[OlegHahm]

Convinced.

[miri64]

(I don't know how trap is working)

[cgundogan]

Actually this is how this script is supposed to work. I do not know why the old solution did not work out

@authmillenon the problem is that set -e exits the whole script once a non-zero exit code was encountered.

Just one question: what if the result is neither one nor zero? Is this also catched?
(I don't know how trap is working)

trap on ERR will be fired for each non-zero exit code. And I just set Result to 1 in that case

[miri64]

Then ACK.

[kaspar030]

Can someone confirm that this PR didn't break the logic? Murdock doesn't seem to exit on doc errors anymore.