branch-distro falls over on branch that didn't scan properly last time

Bug #659666 reported by Michael Hudson-Doyle on 2010-10-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Critical
Unassigned

Bug Description

The branch-distro script fell over like this (https://pastebin.canonical.com/38573/) when it encountered this branch:

   https://code.launchpad.net/~ubuntu-branches/ubuntu/maverick/polybori/maverick

which didn't scan properly when maverick was opened. There are 17 branches that failed like this (https://pastebin.canonical.com/38575/) and it will fall over once for each of them.

The script needs to be more robust about such branches.

Also, we should figure out what's busted about these branches...

Jonathan Lange (jml) on 2010-10-13
tags: added: new-release-cycle-process
Tim Penhey (thumper) on 2010-10-20
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → Medium
Changed in launchpad:
importance: Medium → High
Robert Collins (lifeless) wrote :

This would/should have oopsed; clearly falls under that policy :)

Changed in launchpad:
importance: High → Critical
tags: added: oops
Curtis Hovey (sinzui) on 2012-12-17
description: updated
Curtis Hovey (sinzui) wrote :

I believe we can unscan the each branch now. The fix for this might be for branch-distro's makeOneNewBranch() to call UnscanBranchScript when tip_revision is None, and carry on. When the main queue of branches is completed, it then processes the list unscanned branches. There is a timing issue where the unscan may not have been complete.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers