464859 - automatically generate build comment showing test run / build errors

Status: RESOLVED DUPLICATE of bug 557445

(Release Engineering :: General, defect, P3)

Description

[Mike Beltzner [:beltzner, not reading bugmail]]

Especially when trying to work through intermittent test failures, being able to see *what* caused an orange or red is very important. Right now that requires a click through, and so sheriffs have been clicking through, then copying the error summary from the top into a new build comment.

We should just do that automatically.

Comment 1

[(not currently active) Ted Mielczarek]

The downside to this is that the star general conveys the meaning that someone has looked at this log, so automatically adding stars might give the wrong impression to people. Personally, I'm not a fan of the stars just showing the test failure, as that doesn't tell you whether it's a known intermittent failure, or the result of a new checkin, or what. I find it much more useful when people add comments like "oops, this is a new test, fix committed" or "known intermittent failure - bug 12345".

Comment 2

[Jeff Muizelaar [:jrmuizel]]

You could use a symbol other than a star for automatically added annotations to avoid overloading the fact that star implies some one has looked at the failure
e.g
Star => human anotation
Diamond => automatic annotation

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

This would be implemented in the tinderbox server, no ?

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Now that people are using TBPL, and its just one click, is there anything to do here?

Comment 5

[Johnathan Nightingale [:johnath]]

(In reply to comment #4)
> Now that people are using TBPL, and its just one click, is there anything to do
> here?

I think you're right that TBPL accomplishes this reasonably well (arguably slightly better than the original proposal, since you can *see* the failures in one click, but the build doesn't appear starred). However, I don't think we should close an infrastructure bug off because a third party tool exists that solves the problem - could we instead dup it (or at least reference) to the bug  tracking our efforts to host tbpl ourselves?

Comment 6

[Mike Beltzner [:beltzner, not reading bugmail]]

That would be fine, yes.

Comment 7

[Chris Cooper [:coop] (he/him)]

Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.

Comment 8

[Aki Sasaki (not active)]

This seems like auto-philor, which was duped to bug 557445.