Closed
Bug 713575
Opened 14 years ago
Closed 13 years ago
Brief logs should include the slavename
Categories
(Tree Management Graveyard :: TBPL, defect)
Tree Management Graveyard
TBPL
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: mbrubeck)
References
Details
Attachments
(1 file)
|
1.96 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
If someone gives you a link to a brief log, your only options to see what slave it ran on (when the answer is "it failed like that because the slave is broken") are to load the full log or download the raw log. Given the ridiculous size of some of our logs, that's a lot to get at ten or fifteen characters. We should instead just stick it in the brief log, either as the first line in the "Summary" section or at the end of the "platform test on date for push" line.
| Assignee | ||
Comment 1•13 years ago
|
||
Simple but untested, because I haven't set up a working server deployment yet.
| Assignee | ||
Updated•13 years ago
|
Attachment #609799 -
Flags: review? → review?(mstange)
Comment 2•13 years ago
|
||
Comment on attachment 609799 [details] [diff] [review]
patch
Review of attachment 609799 [details] [diff] [review]:
-----------------------------------------------------------------
You might want to add that to FullLogGenerator as well.
| Assignee | ||
Comment 3•13 years ago
|
||
(In reply to Arpad Borsos (Swatinem) from comment #2)
> You might want to add that to FullLogGenerator as well.
The slave name is already included right at the start of the full log, so I don't think this would be very useful (unless maybe people are writing scrapers or custom userstyles/userscripts that would consume this data somehow).
Updated•13 years ago
|
Attachment #609799 -
Flags: review?(mstange) → review+
| Assignee | ||
Comment 4•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: Webtools → Tree Management
Updated•10 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•