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)
Boards, architectures and test suites: -------------------------------------
hi6220-hikey - arm64 * libhugetlbfs * kselftest * boot * ltp-syscalls-tests
dell-poweredge-r200 - x86_64 * kselftest * libhugetlbfs * boot * ltp-syscalls-tests
Documentation - https://collaborate.linaro.org/display/LKFT/Email+Reports
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 tests would be good to know, and something that I want to get fixed for 4.9.y as I'm guessing this is not the case for 4.14-rc1?
thanks,
greg k-h
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.
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.
tests would be good to know, and something that I want to get fixed for 4.9.y as I'm guessing this is not the case for 4.14-rc1?
For LTP the situation is very similar in terms of results. The only difference I can see is ioctl03 test (which Naresh will check shortly). With kselftest the results also look pretty consistent. There are a few more passes on 4.14-rc1 but I assume they're there because the tested features exist.
milosz
On Mon, Sep 18, 2017 at 06:00:28PM +0100, Milosz Wasilewski 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
Why would NFS matter for these syscalls? Why are you using NFS at all? :)
Two more failed because there is not enough space available: sendfile09 sendfile09_64
How can you find that in the logs? I dug in there, but nothing seemed to be marked with the red "error" color, and then I think I found the error with a blue box of text surrounded by red, but then digging into that didn't result in anything that I could see.
Any hints on how to read the logs?
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.
I did see the ioctl03 "failure" in the log (after digging as I said above), but that was pure luck, and I couldn't see anything other than "failure". Are the test logs stored anywhere?
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.
Ok, but finding out which ones are failing would be good, to verify this.
tests would be good to know, and something that I want to get fixed for 4.9.y as I'm guessing this is not the case for 4.14-rc1?
For LTP the situation is very similar in terms of results. The only difference I can see is ioctl03 test (which Naresh will check shortly). With kselftest the results also look pretty consistent. There are a few more passes on 4.14-rc1 but I assume they're there because the tested features exist.
Getting LTP running would be great, and then adding in the "real" LTP would also be good, as I have caused some recent regressions that our internal testing caught weeks later. We are also starting to see people run VTS and report other real issues that LTP does catch...
thanks,
greg k-h
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
Bug link: https://bugs.linaro.org/show_bug.cgi?id=3250
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
- ./breakpoint_test_arm64: No such file or directory building test cases failed
- 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
- ./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"
- [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&...
tests would be good to know, and something that I want to get fixed for 4.9.y as I'm guessing this is not the case for 4.14-rc1?
For LTP the situation is very similar in terms of results. The only difference I can see is ioctl03 test (which Naresh will check shortly). With kselftest the results also look pretty consistent. There are a few more passes on 4.14-rc1 but I assume they're there because the tested features exist.
milosz
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
On Tue, Sep 19, 2017 at 9:00 AM, Greg KH gregkh@google.com wrote:
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:
- ./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?
Yes, see Documentation/admin-guide/ramoops.rst
ramoops must be configured in one of three ways:
- On device tree based platforms, with a "/reserved-memory/ramoops/" device node that lists the memory location
- With a platform device created from drivers/platform/chrome/chromeos_pstore.c with platform specific data
- Through the kernel command line on platforms that have neither of the other two.
Arnd
On 19 September 2017 at 12:30, Greg KH gregkh@google.com wrote:
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?
You this url in this report https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.50-79-g...
After summary table you see this - look for "complete" jobs only. Test run #31372 Environment: hi6220-hikey Status: Complete and "origin" button. Two ways to get complete test data,
First way: ------------- click on "Test run #31372" That will take you to results summary page. You get to see PASS in green color and FAIL in (baby pink or ) red color. if you want to the reason failure below the summary table of description you get to see Download four buttons. Log file - Test file - Metrics file - Metadata file click on "Log file" "Log file" may get downloaded or you can view in browser (I use google chrome).
Search for failed $(test case name)
Second way: ------------------ "Origin" button takes you to the origin of test job that run on LAVA. https://lkft.validation.linaro.org/scheduler/job/31372 Please search for "selftest" or "fail" etc ... If it LTP job search for $(test case name) or "fail"
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.
I think you know this.
selftests/bpf doesn't compile https://lkml.org/lkml/2017/9/14/336
- ./breakpoint_test_arm64: No such file or directory building test cases failedWhat causes this?
This requires 2 changes: 1. a change in glibc, which I think is done in the latest gcc from linaro. 2. a change in the test code to do #include <asm/ptrace.h> directly instead of relying onto sys/ptrace.h for some struct definitions.
Source of information for bug, https://bugs.linaro.org/show_bug.cgi?id=3208#c1
- 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 upstreamedWhat is the git commit id of this?
Not yet. Patch yet to merge.
[PATCH 2/3] selftests/intel_pstate: No need to compile test progs in the run script Shuah Replied: Thanks for the patch. I will get this into 4.14-rc2 or rc3
https://patchwork.kernel.org/patch/9943785/
- ./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
Bug reported, LKFT: 4.9-rc: Hikey: sysctl.sh need CONFIG_TEST_SYSCTL=y https://bugs.linaro.org/show_bug.cgi?id=3251
- 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?
Hope you found the answer of browsing qa-reports. https://qa-reports.linaro.org/lkft/
- Naresh
thanks,
greg k-h
On Tue, Sep 19, 2017 at 11:06 AM, Naresh Kamboju naresh.kamboju@linaro.org wrote:
On 19 September 2017 at 12:30, Greg KH gregkh@google.com wrote:
On Tue, Sep 19, 2017 at 12:14:56PM +0530, Naresh Kamboju wrote:
You this url in this report https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.50-79-g...
After summary table you see this - look for "complete" jobs only. Test run #31372 Environment: hi6220-hikey Status: Complete and "origin" button. Two ways to get complete test data,
First way:
click on "Test run #31372" That will take you to results summary page. You get to see PASS in green color and FAIL in (baby pink or ) red color. if you want to the reason failure below the summary table of description you get to see Download four buttons. Log file - Test file - Metrics file - Metadata file click on "Log file" "Log file" may get downloaded or you can view in browser (I use google chrome).
Search for failed $(test case name)
Second way:
"Origin" button takes you to the origin of test job that run on LAVA. https://lkft.validation.linaro.org/scheduler/job/31372 Please search for "selftest" or "fail" etc ... If it LTP job search for $(test case name) or "fail"
Didn't at one point clicking on the red 'fail' next you to the result for that test case as it does in kernelci?
I noticed already this is currently broken, but IIRC that was how it was originally done here as well.
Arnd
On Tue, Sep 19, 2017 at 02:36:12PM +0530, Naresh Kamboju wrote:
On 19 September 2017 at 12:30, Greg KH gregkh@google.com wrote:
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?
You this url in this report https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.50-79-g...
After summary table you see this - look for "complete" jobs only. Test run #31372 Environment: hi6220-hikey Status: Complete and "origin" button. Two ways to get complete test data,
First way:
click on "Test run #31372" That will take you to results summary page. You get to see PASS in green color and FAIL in (baby pink or ) red color.
I don't see any red, and scrolling through the whole many many screens to find it doesn't seem to work well.
Trying to "filter out" everything but errors also doesn't work, as that shows me an empty log. So something seems wrong.
if you want to the reason failure below the summary table of description you get to see Download four buttons. Log file - Test file - Metrics file - Metadata file click on "Log file" "Log file" may get downloaded or you can view in browser (I use google chrome).
Search for failed $(test case name)
Second way:
"Origin" button takes you to the origin of test job that run on LAVA. https://lkft.validation.linaro.org/scheduler/job/31372 Please search for "selftest" or "fail" etc ... If it LTP job search for $(test case name) or "fail"
I don't know the name of the test that failed, and searching for "fail" is a lot of matches (144 according to chrome.)
thanks,
greg k-h
On 19 September 2017 at 11:46, Greg KH gregkh@google.com wrote:
On Tue, Sep 19, 2017 at 02:36:12PM +0530, Naresh Kamboju wrote:
On 19 September 2017 at 12:30, Greg KH gregkh@google.com wrote:
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?
You this url in this report https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.50-79-g...
After summary table you see this - look for "complete" jobs only. Test run #31372 Environment: hi6220-hikey Status: Complete and "origin" button. Two ways to get complete test data,
First way:
click on "Test run #31372" That will take you to results summary page. You get to see PASS in green color and FAIL in (baby pink or ) red color.
I don't see any red, and scrolling through the whole many many screens to find it doesn't seem to work well.
Trying to "filter out" everything but errors also doesn't work, as that shows me an empty log. So something seems wrong.
I'm working on presentation right now. The logs aren't easy to work with and it's not possible to separate logs for each test right now. I hope to get this fixed at some point (rather sooner than later). To conclude - I'm aware of the issue and I'm trying to find a solution.
milosz
On 19 September 2017 at 09:44, Naresh Kamboju naresh.kamboju@linaro.org 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
Bug link: https://bugs.linaro.org/show_bug.cgi?id=3250
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
./breakpoint_test_arm64: No such file or directory building test cases failed
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
./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"
[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
It's due to incompatibility between selftests version and kernel version (4.9). The sysctl test driver has been added in 4.14-rc+HEAD in commit 9308f2f9e7f055cf3934645ec622bb5259dc1c14
- 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&...
tests would be good to know, and something that I want to get fixed for 4.9.y as I'm guessing this is not the case for 4.14-rc1?
For LTP the situation is very similar in terms of results. The only difference I can see is ioctl03 test (which Naresh will check shortly). With kselftest the results also look pretty consistent. There are a few more passes on 4.14-rc1 but I assume they're there because the tested features exist.
milosz
Lts-dev mailing list Lts-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lts-dev
-
Arnd Bergmann -
Fathi Boudra -
Greg KH -
Linaro QA -
Milosz Wasilewski -
Naresh Kamboju