Closed
Bug 50269
Opened 25 years ago
Closed 24 years ago
status of yellow builds reported as busted in quickparse output
Categories
(Webtools Graveyard :: Tinderbox, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dbaron, Assigned: mcafee)
Details
Right now medusa is yellow because it has not yet finished its first build since
returning to tinderbox. That is clear from
http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey-Ports
However,
http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey-Ports&quickparse=1
lists it is "busted". This makes techbot1's output wrong.
In the quickparse output it should probably either:
* not be listed until it has status, or
* be listed as "unknown"
Comment 1•25 years ago
|
||
slamm no longer owns tinderbox and is no longer at netscape. Reassigning
to mcafee till a more permenant owner is found so these bugs won't be
ownerless.
Assignee: slamm → mcafee
| Assignee | ||
Comment 2•24 years ago
|
||
I tried this with a new build here:
http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTest&quickparse=1
the new, yellow build doesn't show up in this output.
A resumed build might still be in the history somehow, but how do we
differentiate that from a build that failed and then went yellow for a long
time? This is an edge case I think, let's fix this in tinderbox 2.0.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Updated•11 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•