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