Incorrect publish status when a build has no children

Bug #1210366 reported by Francis Ginther
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Helipad
Fix Released
High
Francis Ginther

Bug Description

This build resulted in a published status when no publish job actually ran:
https://jenkins.qa.ubuntu.com/job/cu2d-mirslave-head/65/console

This build had no children, which isn't handled by the heuristics. Looking through prior runs, this has happened twice in the last 30 runs.

Related branches

Changed in helipad:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Francis Ginther (fginther) wrote :

Before fixing, I've asked jibel and didrocks for an explanation and the correct reporting status.

Revision history for this message
Francis Ginther (fginther) wrote :

According to didrocks, this was not a normal build:
"As I was experimenting on Friday, maybe it did stop it manually and that's why we saw that?"

Regardless, the status should not be published. It should at least have a Failed status.

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:helipad/ci at revision 41, scheduled for release in helipad, milestone Unknown

Changed in helipad:
status: Confirmed → Fix Committed
Changed in helipad:
status: Fix Committed → Fix Released
assignee: nobody → Francis Ginther (fginther)
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.