On Wed, Aug 9, 2017 at 9:58 AM, 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
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.
I like the tags -- they might save some trips to the bug for details. Might be good to indent them though to make it easier on the eye. Eg:
* kselftest/run_vmtests -- failing since build v4.4.77-568946-g4d4632a, from July 21, 2017, 1:28 p.m. CONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3145
* kselftest/fw_filesystem.sh -- never passed IN PROGRESS - https://bugs.linaro.org/show_ bug.cgi?id=2982
* kselftest/test_tag -- never passed CONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3116
* kselftest/test_bpf.sh -- never passed CONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3117 CONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3118