Fail on non-zero exit code from tested subprocess (!12) · Merge requests · Knot projects / deckard · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.

Petr Špaček requested to merge exit_code_check into master Feb 08, 2017

Normally the server process should exit with code 0. Non-zero might indicate crash during shutdown or so.

This can be used for automated Valgrind testing: $ make DAEMON=valgrind ADDITIONAL="--error-exitcode=1 kresd"