lkft/android-hikey-linaro-4.4, build 29e1eb2a96047e17b2b56958d602712c69fda204: 1073 tests, 26 failed, 1046 passed
Tests: 1073 Failed: 26 Passed: 1046 Build: 29e1eb2a96047e17b2b56958d602712c69fda204 Details: https://qa-reports.linaro.org/lkft/android-hikey-linaro-4.4/build/29e1eb2a96...
kernel-describe: 29e1eb2 build-url: https://ci.linaro.org/job/openembedded-lkft-aosp-4.4/DISTRO=rpb,MACHINE=hike... description: Dummy tests kernel-branch: android-hikey-linaro-4.4 format: Lava-Test Test Definition 1.0 series: lkft kernel-commit: 29e1eb2a96047e17b2b56958d602712c69fda204 kernel-repo: https://android.googlesource.com/kernel/hikey-linaro name: dummy-tests kernel-version: 4.4
Regressions (compared to build 84141eaad42ecbffd67ae2780d45305491076258) ------------------------------------------------------------------------
(none)
Failures ------------------------------------------------------------------------
hi6220-hikey:
* pidns -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* run_numerictests -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* fw_filesystem.sh -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* test_lru_map -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* owner -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* test_kmod.sh -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* test_bpf.sh -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* gpio-mockup.sh -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* test_verifier -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* run_stringtests -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* fw_userhelper.sh -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* inconsistency-check -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* test_maps -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* pstore_tests -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* sync_test -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* bitmap.sh -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* seccomp_bpf -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* ftracetest -- failing since build 02c9f20539d0ba3e26737f1a4d242d7bef0b67f5, from May 30, 2017, 5:27 p.m.
* sched_rr_get_interval01 -- failing since build 462886e7a8b900341683bff042358414bd5d4cda, from June 7, 2017, 9:27 p.m.
* sched_rr_get_interval02 -- failing since build 462886e7a8b900341683bff042358414bd5d4cda, from June 7, 2017, 9:27 p.m.
* sched_setparam02 -- failing since build 462886e7a8b900341683bff042358414bd5d4cda, from June 7, 2017, 9:27 p.m.
* sched_setparam03 -- failing since build 462886e7a8b900341683bff042358414bd5d4cda, from June 7, 2017, 9:27 p.m.
* runltp_syscalls -- failing since build 462886e7a8b900341683bff042358414bd5d4cda, from June 7, 2017, 9:27 p.m.
* add_key02 -- failing since build 84141eaad42ecbffd67ae2780d45305491076258, from June 20, 2017, 4:27 p.m.
* sched_getscheduler01 -- failing since build 462886e7a8b900341683bff042358414bd5d4cda, from June 7, 2017, 9:27 p.m.
* sched_rr_get_interval03 -- failing since build 462886e7a8b900341683bff042358414bd5d4cda, from June 7, 2017, 9:27 p.m.
All changes (compared to build 84141eaad42ecbffd67ae2780d45305491076258) ------------------------------------------------------------------------
+---------------------------------+-----------------------------------------------------------+-----------------------------------------------------------+ | Test | 84141eaad42ecbffd67ae2780d45305491076258 (hi6220-hikey) | 29e1eb2a96047e17b2b56958d602712c69fda204 (hi6220-hikey) | +=================================+===========================================================+===========================================================+ | kselftest/raw_skew | pass | | +---------------------------------+-----------------------------------------------------------+-----------------------------------------------------------+ | kselftest/rtctest | pass | | +---------------------------------+-----------------------------------------------------------+-----------------------------------------------------------+ | kselftest/run_vmtests | pass | | +---------------------------------+-----------------------------------------------------------+-----------------------------------------------------------+ | kselftest/test_maps | | fail | +---------------------------------+-----------------------------------------------------------+-----------------------------------------------------------+ | kselftest/test_user_copy.sh | pass | | +---------------------------------+-----------------------------------------------------------+-----------------------------------------------------------+ | kselftest/threadtest | pass | | +---------------------------------+-----------------------------------------------------------+-----------------------------------------------------------+ | kselftest/zram.sh | pass | | +---------------------------------+-----------------------------------------------------------+-----------------------------------------------------------+ | ltp-syscalls-tests/pselect01_64 | fail | pass | +---------------------------------+-----------------------------------------------------------+-----------------------------------------------------------+
-- Linaro QA https://qa-reports.linaro.org
On Wed, Jun 21, 2017 at 2:03 PM, Linaro QA qa-reports@linaro.org wrote:
Summary
- *Tests:* 1073
- *Failed:* 26
- *Passed:* 1046
- *Build:* 29e1eb2a96047e17b2b56958d602712c69fda204
- See details
- *kernel-describe:* 29e1eb2
- *build-url:* https://ci.linaro.org/job/openembedded-lkft-aosp-4.4/
DISTRO=rpb,MACHINE=hikey,label=docker-jessie-amd64/39/ https://ci.linaro.org/job/openembedded-lkft-aosp-4.4/DISTRO=rpb,MACHINE=hikey,label=docker-jessie-amd64/39/
- *description:* Dummy tests
- *kernel-branch:* android-hikey-linaro-4.4
- *format:* Lava-Test Test Definition 1.0
- *series:* lkft
- *kernel-commit:* 29e1eb2a96047e17b2b56958d602712c69fda204
- *kernel-repo:* https://android.googlesource.com/kernel/hikey-linaro
- *name:* dummy-tests
- *kernel-version:* 4.4
I don't think adding the build commit ID in $subject is helpful. it makes the subject line very long and makes it more difficult to read what we really want to see which is the number of pass/fail.
On 21 June 2017 at 13:09, Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
On Wed, Jun 21, 2017 at 2:03 PM, Linaro QA qa-reports@linaro.org wrote:
Summary
Tests: 1073 Failed: 26 Passed: 1046 Build: 29e1eb2a96047e17b2b56958d602712c69fda204 See details
kernel-describe: 29e1eb2 build-url: https://ci.linaro.org/job/openembedded-lkft-aosp-4.4/DISTRO=rpb,MACHINE=hike... description: Dummy tests kernel-branch: android-hikey-linaro-4.4 format: Lava-Test Test Definition 1.0 series: lkft kernel-commit: 29e1eb2a96047e17b2b56958d602712c69fda204 kernel-repo: https://android.googlesource.com/kernel/hikey-linaro name: dummy-tests kernel-version: 4.4
I don't think adding the build commit ID in $subject is helpful. it makes the subject line very long and makes it more difficult to read what we really want to see which is the number of pass/fail.
Seems there are contradicting requirements. The build sha1 was requested by Arnd IIRC. Would truncating to 12 chars make it better? This was also requested and will happen soon.
milosz
On Wed, Jun 21, 2017 at 2:13 PM, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
Seems there are contradicting requirements. The build sha1 was requested by Arnd IIRC. Would truncating to 12 chars make it better? This was also requested and will happen soon.
sure.. truncating should be enough.
On Wed, Jun 21, 2017 at 2:25 PM, Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
On Wed, Jun 21, 2017 at 2:13 PM, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
Seems there are contradicting requirements. The build sha1 was requested by Arnd IIRC. Would truncating to 12 chars make it better? This was also requested and will happen soon.
sure.. truncating should be enough.
Agreed. In the subject, I'd actually use the output of "git describe", i.e. v4.4.72-568859-g29e1eb2a9604 for this branch.
Arnd
On 21 June 2017 at 13:44, Arnd Bergmann arnd@arndb.de wrote:
On Wed, Jun 21, 2017 at 2:25 PM, Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
On Wed, Jun 21, 2017 at 2:13 PM, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
Seems there are contradicting requirements. The build sha1 was requested by Arnd IIRC. Would truncating to 12 chars make it better? This was also requested and will happen soon.
sure.. truncating should be enough.
Agreed. In the subject, I'd actually use the output of "git describe", i.e. v4.4.72-568859-g29e1eb2a9604 for this branch.
Subject uses 'version' of the build. Git sha1 is currently used as a version, but I guess we can move to git describe if that is better in your opinion.
milosz
On Wed, Jun 21, 2017 at 2:50 PM, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On 21 June 2017 at 13:44, Arnd Bergmann arnd@arndb.de wrote:
On Wed, Jun 21, 2017 at 2:25 PM, Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
On Wed, Jun 21, 2017 at 2:13 PM, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
Seems there are contradicting requirements. The build sha1 was requested by Arnd IIRC. Would truncating to 12 chars make it better? This was also requested and will happen soon.
sure.. truncating should be enough.
Agreed. In the subject, I'd actually use the output of "git describe", i.e. v4.4.72-568859-g29e1eb2a9604 for this branch.
Subject uses 'version' of the build. Git sha1 is currently used as a version, but I guess we can move to git describe if that is better in your opinion.
Yes, that sounds good, as its both human-readable and machine-readable.
It might still be a little to long to be repeated many times as in the list of failures, but we could find a different method to deal with that, such as grouping failures that started happening together in one section.
Arnd
On Wed, Jun 21, 2017 at 01:13:18PM +0100, Milosz Wasilewski wrote:
On 21 June 2017 at 13:09, Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
I don't think adding the build commit ID in $subject is helpful. it makes the subject line very long and makes it more difficult to read what we really want to see which is the number of pass/fail.
Seems there are contradicting requirements. The build sha1 was requested by Arnd IIRC. Would truncating to 12 chars make it better? This was also requested and will happen soon.
We need to be able to see it but the subject line isn't quite so essential and it certainly doesn't need to be the first thing. If you look at the existing bots they all use the git describe and they all put it at the *end* of the subject line.
kernel-build-reports@lists.linaro.org
-
Arnd Bergmann -
Linaro QA -
Mark Brown -
Milosz Wasilewski -
Nicolas Dechesne