Closed
Bug 401579
Opened 17 years ago
Closed 15 years ago
RFE: provide a link to the tail of the stdio log
Categories
(Release Engineering :: General, enhancement, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: nthomas, Unassigned)
References
Details
It can take quite a while to download a log from Buildbot just to get to the error at the end. A summary or tail link that returned the last 1000 lines or so would be really helpful. This is sort-of a Tinderbox parity bug, although the Brief log isn't a reliable way to get a tail.
Reporter | ||
Updated•17 years ago
|
Priority: -- → P3
Comment 1•17 years ago
|
||
There's a Buildbot ticket on this, #33. It's marked for 0.9.0 though, which is awhile away. We may want to write a patch to solve that bug to bump it up.
Comment 2•17 years ago
|
||
Correction, Buildbot ticket #32
Updated•17 years ago
|
Assignee: nobody → bhearsum
Updated•17 years ago
|
Status: NEW → ASSIGNED
Priority: P3 → P2
Comment 3•17 years ago
|
||
This is way more complicated than I thought, and not something I can do while working on release automation. Back to the pool for you.
Assignee: bhearsum → nobody
Status: ASSIGNED → NEW
Updated•17 years ago
|
Priority: P2 → P3
Updated•16 years ago
|
Component: Release Engineering → Release Engineering: Future
QA Contact: build → release
Comment 4•15 years ago
|
||
I don't think there's any need to track this here. Upstream ticket: http://buildbot.net/trac/ticket/32
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Comment 5•14 years ago
|
||
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•