Closed
Bug 277089
Opened 21 years ago
Closed 19 years ago
tinderbox panel output should be sorted by build start, not build end
Categories
(Webtools Graveyard :: Tinderbox, defect)
Webtools Graveyard
Tinderbox
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dbaron, Assigned: dbaron)
References
Details
(Whiteboard: [patch])
Attachments
(1 file, 2 obsolete files)
4.40 KB,
patch
|
timeless
:
review+
|
Details | Diff | Splinter Review |
The tinderbox panel output is currently sorted in reverse order by build end.
This isn't all that useful for telling how things are changing. I think it
would be more useful for it to be sorted by build start -- this allows one to
tell if things are turning orange or turning green much more easily.
Patch to follow, except I can't test it. The patch also makes the static
version link to the static full page (no change), and the dynamic one link to
the dynamic full page (change).
Anybody have a tinderbox server this could be tested on?
Assignee | ||
Comment 1•21 years ago
|
||
Assignee | ||
Comment 2•21 years ago
|
||
Attachment #170321 -
Attachment is obsolete: true
Assignee | ||
Updated•21 years ago
|
Whiteboard: [patch]
Comment on attachment 170322 [details] [diff] [review]
patch
+ print "http://tinderbox.mozilla.org/$::tree/";
+ } else {
+ print "http://tinderbox.mozilla.org/showbuilds.cgi?tree=$::tree";
please make that "/$::tree/" and "/showbuilds.cgi?tree=$::tree"
if i did have a tinderbox1 handy, those items wouldn't work because they're
hard coded :(
Attachment #170322 -
Flags: review+
Assignee | ||
Comment 4•21 years ago
|
||
This makes them even more relative than suggested.
Attachment #170322 -
Attachment is obsolete: true
Attachment #170347 -
Flags: review+
Assignee | ||
Comment 5•20 years ago
|
||
Landed tbglobals.pl comment change; still need to test showbuilds.cgi change.
Comment 6•20 years ago
|
||
When you have it, please offer a link to an example of this change in action.
Assignee | ||
Comment 7•19 years ago
|
||
Checked in, since this was tested on the live instance (bug 333778).
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
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
•