On Thu, 3 Oct 2019 at 04:15, Daniel Díaz <daniel.diaz@xxxxxxxxxx> wrote: > > Hello! > > On Wed, 2 Oct 2019 at 20:52, shuah <shuah@xxxxxxxxxx> wrote: > > > > On 10/2/19 7:00 AM, ci_notify@xxxxxxxxxx wrote: > > > Summary > > > ------------------------------------------------------------------------ > > > kernel: 5.4.0-rc1 > > > git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > > > git branch: master > > > git commit: a32db7e1172439240202b843642465618498170d > > > git describe: next-20191002 > > > Test details: https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20191002 > > > > > > Regressions (compared to build next-20191001) > > > > This report is nice for quick glance of test pass/fail/skip dashboard. > > I am finding very difficult to figure out why the test failed. > > > > Can you please save the test run logs and stash them for access? > > Logs are saved. You can click on the test details: > https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20191002 > then opening "kselftests" in Test Results, choosing an environment > (say "x86_64"), and then (here's the tricky one) "job_url": > https://lkft.validation.linaro.org/scheduler/job/948404 If you want to download the log and do grep locally you can find that under "Related downloads" the button "Log file" that will download the complete log also. Cheers, Anders [1] https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20191002/testrun/948404/ > Running kselftests starts in line 1276 in that particular log. > > Hope that sheds some light on that. > > Greetings! > > Daniel Díaz > daniel.diaz@xxxxxxxxxx
