cu2d-trigger should fail gracefully if no projects are defined in stack
Bug #1164041 reported by
Martin Mrazik
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cupstream2distro Configuration |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This is what happens when no projects are defined in the stack:
2013-04-03 17:05:26,216 DEBUG Loading stack configuration from ../stacks/
Traceback (most recent call last):
File "./cu2d-trigger", line 39, in <module>
sys.
File "./../c2dconfig
for trigger in trigger_list:
UnboundLocalError: local variable 'trigger_list' referenced before assignment
Related branches
lp:~fginther/cupstream2distro-config/fix-empty-projects
- Chris Gagnon (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 94 lines (+35/-2)4 files modifiedc2dconfigutils/cu2dTrigger.py (+5/-1)
c2dconfigutils/cu2dWatchDog.py (+4/-1)
tests/test_CheckStalledMPs.py (+15/-0)
tests/test_cu2dTrigger.py (+11/-0)
Changed in cupstream2distro-config: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in cupstream2distro-config: | |
status: | Triaged → Fix Released |
To post a comment you must log in.