cu2d-trigger should fail gracefully if no projects are defined in stack

Bug #1164041 reported by Martin Mrazik
6
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/raring/misc.cfg
Traceback (most recent call last):
  File "./cu2d-trigger", line 39, in <module>
    sys.exit(command(BASEDIR))
  File "./../c2dconfigutils/cu2dTrigger.py", line 142, in __call__
    for trigger in trigger_list:
UnboundLocalError: local variable 'trigger_list' referenced before assignment

Related branches

Martin Mrazik (mrazik)
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.
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.