Closed
Bug 631293
Opened 15 years ago
Closed 12 years ago
change status number for strings on buildapi
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: armenzg, Unassigned)
Details
(Keywords: buildapi)
For https://build.mozilla.org/buildapi/recent/talos-r3-leopard-009
and https://build.mozilla.org/buildapi/recent
we have numbers/bg colours to represent status:
1/green - means SUCCESS
2/red - means FAILURE
3/orange - means WARNING
which are known to most people but we have other codes which are not that clear to developers.
5/grey - I think it means RETRY.
Could we add a legend or substitute the numbers for a string?
Added ehsan as he was tooooooooo lazy & slow to file this simple bug so I decided he would still be like that to even CC himself :P
Comment 1•15 years ago
|
||
ITYM
0/green - SUCCESS in buildbot
1/orange - WARNING - test failure
2/red - FAILURE - compilation failure (and any infra exceptions we don't have in 4 yet)
4/purple - EXCEPTION - something failed with the slave or the infra it talks to
5/grey - RETRY - generally as a result of something that caused a EXCEPTION
These are defined at
http://hg.mozilla.org/build/buildbot/file/9fef016867c7/master/buildbot/status/builder.py#l25
With the exception of RETRY these all the same as used on TBPL/Tinderbox. So does this boil down to 'please add a legend' ?
Updated•15 years ago
|
OS: Mac OS X → All
Priority: -- → P3
Hardware: x86 → All
Whiteboard: [buildapi]
| Reporter | ||
Comment 2•15 years ago
|
||
legend should be good enough.
| Assignee | ||
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•