Launchpad itself

protocol-mismatch fails to record reason for failing a builder

Bug #2637 reported by Daniel Silverstone
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

When a builder is failed for an XMLRPC protocol mismatch, we don't record this in the builder properly so we never get to see why the builder is marked as not-okay.

Revision history for this message
Daniel Silverstone (dsilvers) wrote :

Clearly uninteresting after more than a year

Changed in soyuz:
status: Unconfirmed → Rejected
Revision history for this message
Celso Providelo (cprov) wrote :

Just because it's old doesn't mean that it doesn't need fix. The bug is still there and will be fixed when we have time.

Changed in soyuz:
importance: Medium → Wishlist
status: Rejected → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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