On Thu, Mar 15, 2018 at 10:12 AM, Linaro QA qa-reports@linaro.org wrote:
Summary
kernel: 4.16.0-rc5 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git branch: master git commit: 3032f8c504d2b15d58e4c96060a96b47e215573c git describe: v4.16-rc5-46-g3032f8c504d2 Test details: https://qa-reports.linaro.org/lkft/linux-mainline-oe/build/v4.16-rc5-46-g303...
No regressions (compared to build v4.16-rc5-4-gfc6eabbbf8ef)
Boards, architectures and test suites:
dragonboard-410c
- boot - fail: 39
We need to reconcile this failure with the subject line to allow better filtering of email.
While it is true that there are no regressions compared to a previous build from a few hours ago, a boot failure is a huge regression from the "baseline". We should be blaring horns and flashing lights to draw attention to it. :-) I know the QCLT is serious about tracking and fixing these as soon as possible.
So here are a few proposals to improve the report:
1. Convert these statistics to searchable keyboards that I can setup email filters on.
e.g. dragonboard-410c * boot - fail: 39
might become,
dragonboard-410c: boot: fail
(Is 39 the number of times a boot was attempted?)
2. Change the subject on this email to reflect that regressions still exist but nothing changed from the previous build. If possible point to the last build where this failure was NOT present.
3. Add some easy to search keywords in the email instead of resorting to pattern matching. This removes the need for proposal 1.
I see from a previous report the following summary, so lkft did warn us but it got lost in the noise. Most times we'd like to only know if db410c fails. How can we achieve that? Perhaps adding a unique keyword e.g. DB410CBOOTFAIL somewhere in the email? Doesn't need to be in your nicely formatted summary. I can then safely ignore all "regression found" email that don't have the keyword.
Regressions (compared to build v4.14.26) ------------------------------------------------------------------------
dragonboard-410c: boot: * dragonboard-410c
* test src: not informed
hi6220-hikey - arm64: boot: * hi6220-hikey
* test src: not informed