Running undefined subcommands gives a traceback

Bug #639930 reported by Paul Larson
8
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/ltcteam/abrek.sep15/abrek/main.py", line 31, in main
    main(argv)
  File "/home/ltcteam/abrek.sep15/abrek/command.py", line 69, in main
    return self.run()
  File "/home/ltcteam/abrek.sep15/abrek/command.py", line 76, in run
    self.name())
NotImplementedError: results: command defined but not implemented!

Related branches

Paul Larson (pwlars)
Changed in abrek:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Paul Larson (pwlars)
Paul Larson (pwlars)
Changed in abrek:
status: In Progress → Fix Committed
Paul Larson (pwlars)
Changed in abrek:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.