On 9 August 2017 at 17:58, Steve Muckle <smuckle@google.com> wrote:

On Wed, Aug 9, 2017 at 7:30 AM, Tom Gall <tom.gall@linaro.org> wrote:
So on these reports, there is a thought by the team to map the test
bucket & test case when they are known fails back to the bugzilla
entry or some meta for however/whereever it's being tracked.

That mechanism doesn't as of yet exist but sounds like something we'll
look at implementing at some point.

So until that exists it's a bit of a manual process but I think a
worthwhile one to do.

+1

One question I have is if we're anticipating having bugs that are long enough lived to be worth tracking the status of - I'd anticipate that this is going to be more likely with the larger testsuites like the Android ones so perhaps but...

I've done a slight (ugly) mock up to given an idea.

Remember :
UNCONFIRMED : Triage not complete
CONFIRMED : Triage complete, bug under discussion on how best to move forward
IN_PROGRESS : Team actively working on bug

I'm wondering if these tags are worth putting in the email? They seem a bit distracting to my eye, especially in all-caps, and I'm guessing most folks will always just want to go read the bug to find out what's going on with a failing test.

...it also means that we'd be restricted to using a bug tracker we can parse which might complicate things when for example the upstream has a bug tracker and it makes sense to use that one directly (like if they're actively engaged with LKFT or they've already found the same problem and are tracking it themselves). If it's just a link then we can point to anywhere that makes sense.