Closed Bug 516443 Opened 15 years ago Closed 14 years ago

Make buildsteps output the status of how they finished

Categories

(Release Engineering :: General, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 522792

People

(Reporter: armenzg, Unassigned)

Details

We have bugs steps that they end with warnings or errors but do not necessarily output it to the log and therefore the tinderbox parser does not pick it up.

At some point (not that close in time but we are working on it) we will move away from Tinderbox and these things won't be a problem anymore. But until we reach that point I believe it makes sense to do something so at least developers can have a way of figuring out which step caused the warning or error.

A way of mitigating this in a general way rather than a per case basis would be to take advantage that we already output when a step finishes and where the next one starts to indicate the status. By doing so, developers at least would be able to tell which step failed even if the step in itself did not generate output to realize that it failed or raised warnings. 

See for instance bugs 499784 and bug 516421.
Priority: P3 → P4
I won't be able to work on this for a while putting back into the pool
Assignee: armenzg → nobody
Status: ASSIGNED → NEW
Component: Release Engineering → Release Engineering: Future
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.