Invalid external_dependencies can kill buildd-manager

Bug #516169 reported by Julian Edwards
262
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Muharem Hrnjadovic

Bug Description

An buggy external dependencies line recently caused the buildd-manager to continually fail its scan, because the "series" substitution was specified as %(series) instead of %(series)s

We should disable the PPA if there is an exception when processing external_dependencies, and continue.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

In adapters/archivedependencies.py, in the function get_sources_list_for_building(), it should catch any exceptions when processing build.archive.external_dependencies.

I'm not sure how we can make the buildd-manager ignore the current build, but that should happen when disabling the PPA.

Changed in soyuz:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Muharem Hrnjadovic (al-maisan)
milestone: none → 10.02
Revision history for this message
LaMont Jones (lamont) wrote :

pretty much any exception handling a ppa should just disable the ppa, instead of build-manager. :-(

tags: added: buildd-manager
Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 516169] Re: Invalid external_dependencies can kill buildd-manager

On Tuesday 02 February 2010 18:14:55 LaMont Jones wrote:
> pretty much any exception handling a ppa should just disable the ppa,
> instead of build-manager. :-(
>

Sometimes it's just a bad build, so a blanket rule like this won't work. We
need to be more intelligent about the kinds of errors that happen.

Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

> I'm not sure how we can make the buildd-manager ignore the current
> build, but that should happen when disabling the PPA.
Since the external dependencies are incorrect there's a high chance that
the current build will fail.
Any other pending builds associated with the PPA in question will be
suspended (and hence ignored by the buildd manager) as soon as the PPA
is disabled.

Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

The branch that fixes this bug was tested on mawson and the effects
observed are as follows: when a candidate build job targeting a PPA with
a garbled 'external_dependencies' property is considered for dispatch
the
- PPA gets disabled
- buildd manager does dispatch the job. That's not optimal
  *but* not that bad in practical terms either because
  - that job is bound to fail early on due to unsatisfied external
    dependencies
  - even if the job builds OK the resulting binaries will fail to upload
    since the PPA was disabled in the meantime
- buildd manager does not fall over

Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit
Changed in soyuz:
status: In Progress → Fix Committed
Changed in soyuz:
status: Fix Committed → Fix Released
William Grant (wgrant)
visibility: private → public
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.