Assertion failed: self.builder == builder

Bug #1960132 reported by Mc
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Colin Watson

Bug Description

A build failed ( https://code.launchpad.net/~inkscape.dev/+archive/ubuntu/stable-1.1/+build/23129869 ) without detailing the failure reason.

Upon investigation by cjwatson, internal logs are https://paste.ubuntu.com/p/dhmPZdXpFK/

Related branches

Revision history for this message
Colin Watson (cjwatson) wrote :

I suspect that following https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/414070 we may need to do a little more work to completely reset builds on retry.

summary: - builder fails without providing logs
+ Assertion failed: self.builder == builder
Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
tags: added: buildd-manager buildfarm regression
Revision history for this message
Colin Watson (cjwatson) wrote :

Specifically, I think we probably need to start clearing `self.specific_build.builder` in `BuildQueue.reset`.

Colin Watson (cjwatson)
Changed in launchpad:
assignee: nobody → Colin Watson (cjwatson)
status: Triaged → In Progress
Colin Watson (cjwatson)
Changed in launchpad:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers