On Tue, Sep 19, 2017 at 12:14:56PM +0530, Naresh Kamboju wrote:
On 18 September 2017 at 22:30, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On 18 September 2017 at 17:25, Greg KH gregkh@google.com wrote:
On Mon, Sep 18, 2017 at 11:47:16AM +0000, Linaro QA wrote:
Summary
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: 8d96ea41a3ee57a7a145054e57fe0fb1a5d19861 git describe: v4.9.50-79-g8d96ea41a3ee Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.50-79-g...
No regressions (compared to build v4.9.50)
No regressions is good, but why do we have so many actual failures overall? Seeing that we are failing 15 kselftests and 12 ltp syscall
The LTP tests fail mostly because of NFS. This only applies to x86 where we mount rootfs this way. These tests pass on HiKey
flock01 flock04 linkat01 open12 openat02 renameat201 renameat202 utime01 utime02 utime03
Two more failed because there is not enough space available: sendfile09 sendfile09_64
In these results I can see flock actually passing and ioctl03 failing. Naresh, could you take a look? I didn't see the bug for that in our bugzilla.
LTP test case ioctl03 failed due to missing CONFIG_TUN=y on linux-stable-rc-4.9 on x86 device.
ioctl03 test PASS when, CONFIG_TUN=y is on Hikey on linux-stable-rc-4.9 CONFIG_TUN=m is on x86 on linux-next
Thanks for the info, but my other questions remain, how could I have figured this out from the test reports? I'm guessing it was burried in there somewhere? Any pointers to how to find it?
I'm not 100% sure about kselftest but these failures are most likely due to incompatibility between test version (coming from 4.13) and kernel version. Not all tests can fail gracefully when the tested feature is not available.
The reasons for 15 kselftest failures on Hikey device running linux-stable-rc-4.9.
On linux-stable-rc-4.9 Hikey:
- kselftest failures
- All 8 bpf tests failed due to missing test programs on target building test cases failed
Expected.
- ./breakpoint_test_arm64: No such file or directory building test cases failed
What causes this?
- intel_pstate - gcc: error: aperf.c: No such file or directory building test cases failed due to missing source on target Fix: do not compile on target Fix patch upstreamed
What is the git commit id of this?
- ./run_fuse_test.sh: line 12: 3330 Bus error ./fuse_test ./mnt/memfd Bug is under investigation - which failed on all Linux versions - Checking pstore console is registered ... FAIL Checking /dev/pmsg0 exists ... FAIL Writing unique string to /dev/pmsg0 ... FAIL Bug reported - This test need extra kernel command line arguments "backend=ramoops ramoops.mem_address=0x30000000 ramoops.mem_size=0x10000"
Odd, is this a pstore requirement?
- [ERROR] Failure triggering fence [FAIL] sync errors: 1 selftests: sync_test [FAIL] bug is under investigation - sysctl.sh failed modprobe: FATAL: Module test_sysctl not found in directory
/lib/modules/4.9.51-rc1-00079-g8d96ea4-dirty ./sysctl.sh: /sys/module/test_sysctl/ not present You must have the following enabled in your kernel: cat: ./config: No such file or directory Failed due to missing Kconfig - CONFIG_TEST_SYSCTL=y
- Running userfaultfd_shmem nr_pages: 32768, nr_pages_per_cpu: 4096 bounces: 31, mode: rnd racing ver poll, register failure selftests: run_vmtests [FAIL] Bug is under investigation.
LAVA job running kselftests: https://lkft.validation.linaro.org/scheduler/job/31372#L1246
Bugs link: https://bugs.linaro.org/buglist.cgi?list_id=14965&query_format=advanced&...
Same question as above, how could I have seen this myself?
thanks,
greg k-h