Changes become severed heads too late
Bug #1138592 reported by
James E. Blair
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zuul |
New
|
Undecided
|
Unassigned | ||
Bug Description
Changes are not becoming severed heads until the result of the job _after_ the failed change is reported.
In other words:
1) Jobs A, B, C are started for a change at the head
2) A fails
3) B succeeds
4) the change is severed
But the change should have been severed immediately after A failed.
To post a comment you must log in.
