[Buildbot-commits] [Buildbot] #778: 'latest' revision get's stuck on grid views when source step fails

[Buildbot]

#778: 'latest' revision get's stuck on grid views when source step fails
--------------------+-------------------------------------------------------
Reporter:  marcusl  |       Owner:       
    Type:  defect   |      Status:  new  
Priority:  major    |   Milestone:  0.9.+
 Version:  0.7.12   |    Keywords:  web  
--------------------+-------------------------------------------------------

Comment(by dustin):

 My thinking was that the earliest build is probably more indicative of the
 "natural" order of the builds; any time after that is due to builder
 contention, most likely.  So if I have five builds of rev X at 7pm and one
 at 9pm, probably that change should sort earlier than a build that
 occurred at 7:30 - that 9pm build was probably due to a downed or slow
 slave or something like that.

 To your particular issue - the problem is really that infrastructural
 issues are clouding your build status.  If the checkout had succeeded but
 another non-code-related step failed, you'd get the same result, right?

 Mozilla's done a decent job of categorizing certain kinds of failures as
 orange, red, or purple, but that's mostly been ad-hoc and done by patching
 various error-handling situations and special-casing the things that turn
 out the wrong color.  I wonder if there's some more general way to do
 that?

-- 
Ticket URL: <http://buildbot.net/trac/ticket/778#comment:8>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation