lkft/android-hikey-linaro-4.4-oe: 1120 tests, 25 failed, 1093 passed (build v4.4.80-568084-g7f6b98c)
Tests: 1120 Failed: 25 Passed: 1093 Skipped: 2 Build: v4.4.80-568084-g7f6b98c Details: https://qa-reports.linaro.org/lkft/android-hikey-linaro-4.4-oe/build/v4.4.80...
kernel-repo: https://android.googlesource.com/kernel/hikey-linaro kernel-commit: 7f6b98cd2c87e10f51b934b254662e9d73b7b115 kernel-describe: v4.4.80-568084-g7f6b98c kernel-config: https://snapshots.linaro.org/openembedded/lkft/morty/hikey/rpb/4.4/61/defcon... kernel-branch: android-hikey-linaro-4.4 build-url: https://ci.linaro.org/job/openembedded-lkft-aosp-4.4/DISTRO=rpb,MACHINE=hike... series: lkft
Regressions ------------------------------------------------------------------------
(none)
Failures ------------------------------------------------------------------------
hi6220-hikey:
* kselftest/run_vmtests -- failing since build v4.4.77-568946-g4d4632a, from July 21, 2017, 1:28 p.m. * kselftest/fw_filesystem.sh -- never passed * kselftest/test_tag -- never passed * kselftest/test_bpf.sh -- never passed * kselftest/test_align -- never passed * kselftest/run.sh -- never passed * kselftest/test_kmod.sh -- never passed * kselftest/test_lru_map -- never passed * ltp-syscalls-tests/utimensat01 -- never passed * kselftest/seccomp_bpf -- never passed * ltp-syscalls-tests/pselect01_64 -- failing since build v4.4.79-568979-g43c93f7, from Aug. 1, 2017, 10:12 p.m. * kselftest/inconsistency-check -- never passed * ltp-syscalls-tests/runltp_syscalls -- never passed * kselftest/breakpoint_test_arm64 -- never passed * kselftest/pidns -- never passed * kselftest/ftracetest -- never passed * kselftest/test_maps -- never passed * kselftest/fw_fallback.sh -- never passed * kselftest/test_lpm_map -- never passed * kselftest/bitmap.sh -- never passed * kselftest/pstore_tests -- never passed * kselftest/gpio-mockup.sh -- never passed * kselftest/test_verifier -- never passed * kselftest/run_fuse_test.sh -- never passed * kselftest/owner -- never passed
All changes ------------------------------------------------------------------------
(none)
-- Linaro QA (beta) https://qa-reports.linaro.org
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.
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
On Mon, Aug 7, 2017 at 6:48 PM, Linaro QA qa-reports@linaro.org wrote:
Tests: 1120 Failed: 25 Passed: 1093 Skipped: 2 Build: v4.4.80-568084-g7f6b98c Details: https://qa-reports.linaro.org/lkft/android-hikey-linaro-4.4-oe/build/v4.4.80...
kernel-repo: https://android.googlesource.com/kernel/hikey-linaro kernel-commit: 7f6b98cd2c87e10f51b934b254662e9d73b7b115 kernel-describe: v4.4.80-568084-g7f6b98c kernel-config: https://snapshots.linaro.org/openembedded/lkft/morty/hikey/rpb/4.4/61/defcon... kernel-branch: android-hikey-linaro-4.4 build-url: https://ci.linaro.org/job/openembedded-lkft-aosp-4.4/DISTRO=rpb,MACHINE=hike... series: lkft
Regressions
(none)
Failures
hi6220-hikey:
- 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
- kselftest/test_align -- never passed
UNCONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3170
- kselftest/run.sh -- never passed
- kselftest/test_kmod.sh -- never passed
IN_PROGRESS - https://bugs.linaro.org/show_bug.cgi?id=3114
- kselftest/test_lru_map -- never passed
CONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3118
- ltp-syscalls-tests/utimensat01 -- never passed
CONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3142
- kselftest/seccomp_bpf -- never passed
IN_PROGRESS - https://bugs.linaro.org/show_bug.cgi?id=2980
- ltp-syscalls-tests/pselect01_64 -- failing since build v4.4.79-568979-g43c93f7, from Aug. 1, 2017, 10:12 p.m.
IN_PROGRESS - https://bugs.linaro.org/show_bug.cgi?id=3089
- kselftest/inconsistency-check -- never passed
- ltp-syscalls-tests/runltp_syscalls -- never passed
- kselftest/breakpoint_test_arm64 -- never passed
- kselftest/pidns -- never passed
- kselftest/ftracetest -- never passed
- kselftest/test_maps -- never passed
CONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3117
- kselftest/fw_fallback.sh -- never passed
- kselftest/test_lpm_map -- never passed
CONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3119
- kselftest/bitmap.sh -- never passed
- kselftest/pstore_tests -- never passed
IN_PROGRESS - https://bugs.linaro.org/show_bug.cgi?id=3005
- kselftest/gpio-mockup.sh -- never passed
- kselftest/test_verifier -- never passed
UNCONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3170
- kselftest/run_fuse_test.sh -- never passed
CONFIRMED - https://bugs.linaro.org/show_bug.cgi?id=3123
- kselftest/owner -- never passed
All changes
(none)
-- Linaro QA (beta) https://qa-reports.linaro.org _______________________________________________ Lts-dev mailing list Lts-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lts-dev
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.
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.
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
-
Linaro QA -
Mark Brown -
Steve Muckle -
Todd Kjos -
Tom Gall