Running undefined subcommands gives a traceback
Bug #639930 reported by
Paul Larson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Obsolete LAVA Test |
Fix Released
|
Medium
|
Paul Larson |
Bug Description
Deepti pointed out to me today that if you try to run an undefined subcommand you get a traceback instead of a more useful error:
bin/abrek results lists
Traceback (most recent call last):
File "bin/abrek", line 30, in <module>
exit_code = abrek.main.main()
File "/home/
main(argv)
File "/home/
return self.run()
File "/home/
self.name())
NotImplementedE
Related branches
lp:~pwlars/lava-test/bug639930
- James Westby (community): Needs Information
-
Diff: 111 lines (+51/-13)5 files modifiedabrek/main.py (+15/-11)
bin/abrek (+1/-1)
tests/__init__.py (+1/-0)
tests/imposters.py (+3/-1)
tests/test_main.py (+31/-0)
Changed in abrek: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Paul Larson (pwlars) |
Changed in abrek: | |
status: | In Progress → Fix Committed |
Changed in abrek: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.