Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Indicate result via exit code
See original GitHub issueCurrently mutmut run and result always exits with code 0.
It would be very useful (e.g. for inclusion in CI systems) if both could give a return code depending on the type of found issues.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Understanding Exit Codes and Using them in Bash scripts
On Unix and Linux systems, programs can pass a value to their parent process while terminating. This value is referred to as an...
Read more >Linux and Unix exit code tutorial with examples - George Ornbo
Tutorial on using exit codes from Linux or UNIX commands. Examples of how to get the exit code of a command, how to...
Read more >Chapter 6. Exit and Exit Status
The exit command terminates a script, just as in a C program. · Every command returns an exit status (sometimes referred to as...
Read more >Returning information from a shell script via an Exit Code
Exit codes are a number between 0 and 255, which is returned by any Unix command when it returns control to its parent...
Read more >Bash command line exit codes demystified | Enable Sysadmin
An exit code is a system response that reports success, an error, or another condition that provides a clue about what caused an...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ulope ok, thanks for your feedback. Then I suggest we do what @nklapste suggests.
@nklapste can you maybe make a PR with just this change?
I’ve rolled a 1.2.0 release that includes this now.