Tests: 2517 Failed: 36 Passed: 2166 Skipped: 315 Build: next-20170913 Details: https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20170913
kselftest__url: https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.13.tar.xz kernel-repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git kernel-branch: master ltp-syscalls-tests__version: 20170516 kernel-commit: 6f20b7a58cb9c0fe00badcdfd65b1f4a8f28dfc6 libhugetlbfs__url: git://github.com/libhugetlbfs/libhugetlbfs.git kselftest__version: 4.13 kernel-describe: next-20170913 libhugetlbfs__revision: e44180072b796c0e28e53c4d01ef6279caaa2a99 ltp-syscalls-tests__revision: 6c6c6ca40afb3611e52486f670085762ff451e91 series: lkft ltp-syscalls-tests__url: git://github.com/linux-test-project/ltp.git libhugetlbfs__version: 2.20
Regressions (compared to build next-20170912) ------------------------------------------------------------------------
(none)
Failures ------------------------------------------------------------------------
x86:
* kselftest/pstore_tests -- never passed * ltp-syscalls-tests/sendfile09_64 -- never passed * ltp-syscalls-tests/linkat01 -- never passed * kselftest/run_vmtests -- never passed * ltp-syscalls-tests/renameat202 -- never passed * kselftest/ftracetest -- never passed * kselftest/run_fuse_test.sh -- never passed * ltp-syscalls-tests/flock01 -- never passed * ltp-syscalls-tests/openat02 -- never passed * kselftest/run.sh -- never passed * ltp-syscalls-tests/utimes01 -- never passed * ltp-syscalls-tests/runltp_syscalls -- never passed * ltp-syscalls-tests/flock04 -- never passed * ltp-syscalls-tests/utime01 -- never passed * ltp-syscalls-tests/renameat201 -- never passed * kselftest/test_kmod.sh -- never passed * ltp-syscalls-tests/io_submit01 -- never passed * ltp-syscalls-tests/sendfile09 -- never passed * ltp-syscalls-tests/open12 -- never passed * kselftest/test_progs -- failing since build next-20170905, from Sept. 5, 2017, 7:01 a.m. * kselftest/test_align -- failing since build next-20170905, from Sept. 5, 2017, 7:01 a.m. * ltp-syscalls-tests/utime02 -- never passed * ltp-syscalls-tests/utime06 -- never passed * kselftest/test_verifier -- never passed hi6220-hikey:
* kselftest/test_maps -- never passed * kselftest/ftracetest -- never passed * kselftest/run_vmtests -- failing since build next-20170713, from July 13, 2017, 4:28 p.m. * kselftest/test_verifier -- never passed * kselftest/seccomp_bpf -- failing since build next-20170810, from Aug. 10, 2017, 7:03 a.m. * kselftest/test_kmod.sh -- never passed * kselftest/breakpoint_test_arm64 -- never passed * kselftest/run_fuse_test.sh -- never passed * kselftest/test_align -- never passed * kselftest/run.sh -- never passed * kselftest/test_progs -- failing since build next-20170905, from Sept. 5, 2017, 7:01 a.m. * kselftest/pstore_tests -- never passed
All changes (compared to build next-20170912) ------------------------------------------------------------------------
+--- next-20170912, hi6220-hikey - arm64 | +--- next-20170913, hi6220-hikey - arm64 | | +--- next-20170912, dell-poweredge-r200 - x86_64 | | | +--- next-20170913, dell-poweredge-r200 - x86_64 | | | | fail pass pass pass kselftest/test_lru_map
-- Linaro QA (beta) https://qa-reports.linaro.org
On Wed, Sep 13, 2017 at 12:03:55PM +0000, Linaro QA wrote:
kselftest__url: https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.13.tar.xz kernel-repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git kernel-branch: master ltp-syscalls-tests__version: 20170516 kernel-commit: 6f20b7a58cb9c0fe00badcdfd65b1f4a8f28dfc6 libhugetlbfs__url: git://github.com/libhugetlbfs/libhugetlbfs.git kselftest__version: 4.13 kernel-describe: next-20170913 libhugetlbfs__revision: e44180072b796c0e28e53c4d01ef6279caaa2a99 ltp-syscalls-tests__revision: 6c6c6ca40afb3611e52486f670085762ff451e91 series: lkft ltp-syscalls-tests__url: git://github.com/linux-test-project/ltp.git libhugetlbfs__version: 2.20
This is hard to read to the point where it's effectively just noise. There's no obvious ordering or grouping of the information and the layout isn't very regular which makes parsing it more difficult.
I think the testsuite stuff should be split out from the description of the kernel being tested, and probably presented as a table rather than a splat of key/value pairs (the __s in the key names are also weird). There's no need to use the full hashes for the commit IDs, just using the 12 character abberviation should be enough, which should make that a lot more tractable.
On Wed, Sep 13, 2017 at 08:11:27AM -0700, Mark Brown wrote:
On Wed, Sep 13, 2017 at 12:03:55PM +0000, Linaro QA wrote:
kselftest__url: https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.13.tar.xz kernel-repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git kernel-branch: master ltp-syscalls-tests__version: 20170516 kernel-commit: 6f20b7a58cb9c0fe00badcdfd65b1f4a8f28dfc6 libhugetlbfs__url: git://github.com/libhugetlbfs/libhugetlbfs.git kselftest__version: 4.13 kernel-describe: next-20170913 libhugetlbfs__revision: e44180072b796c0e28e53c4d01ef6279caaa2a99 ltp-syscalls-tests__revision: 6c6c6ca40afb3611e52486f670085762ff451e91 series: lkft ltp-syscalls-tests__url: git://github.com/linux-test-project/ltp.git libhugetlbfs__version: 2.20
This is hard to read to the point where it's effectively just noise. There's no obvious ordering or grouping of the information and the layout isn't very regular which makes parsing it more difficult.
I think the testsuite stuff should be split out from the description of the kernel being tested, and probably presented as a table rather than a splat of key/value pairs (the __s in the key names are also weird). There's no need to use the full hashes for the commit IDs, just using the 12 character abberviation should be enough, which should make that a lot more tractable.
There was no response to this, any thoughts?
kernel-build-reports@lists.linaro.org
-
Linaro QA -
Mark Brown