mojo should not return 0 when printing usage information
Bug #1540994 reported by
Neale Pickett
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mojo: Continuous Delivery for Juju |
Confirmed
|
Low
|
Unassigned |
Bug Description
We just finished debugging an issue wherein mojo was returning 0 when we passed the wrong arguments, giving our CI run no indication of a problem:
ubuntu@
0
Mojo should return non-zero when command-line arguments are incorrect. EX_USAGE (64) as defined in /usr/include/
Changed in mojo: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: papercut |
To post a comment you must log in.
This appears to be argparser behaviour. See http:// stackoverflow. com/questions/ 5943249/ python- argparse- and-controlling -overriding- the-exit- status- code and https:/ /www.python. org/dev/ peps/pep- 0389/#discussio n-sys-stderr- and-sys- exit particularly.