On 29 March 2018 at 17:30, Amit Kucheria amit.kucheria@linaro.org wrote:
On Thu, Mar 29, 2018 at 2:09 PM, Linaro QA qa-reports@linaro.org wrote:
Summary
kernel: 4.16.0-rc7 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git branch: master git commit: a2601d78b77aacc5dd790f488188f9556f4a9eb2 git describe: v4.16-rc7-46-ga2601d78b77a Test details: https://qa-reports.linaro.org/lkft/linux-mainline-oe/build/v4.16-rc7-46-ga26...
Regressions (compared to build v4.16-rc6-459-gcb6416592bc2)
dragonboard-410c: boot: * dragonboard-410c
* test src: not informedBoards, architectures and test suites:
dragonboard-410c
- boot - fail: 3, pass: 16
Should we care about this given that there are only 3 failures out of 19? The log[1] is a bit sparse.
Can this be put down to "infrastructure issues" ?
Yes. It is an "infrastructure issues" for 3 boot fail cases. We need to enable 2nd UART. because In LAVA automation login prompt overwritten by dmesg logs. LAVA reported auto-login failure.
- Naresh
[1] https://qa-reports.linaro.org/lkft/linux-mainline-oe/build/v4.16-rc7-46-ga26...
- kselftest - skip: 18, fail: 3, pass: 48
- ltp-containers-tests - skip: 17, pass: 64
- ltp-fcntl-locktests-tests - pass: 2
- ltp-filecaps-tests - pass: 2
- ltp-fs-tests - skip: 2, pass: 61
- ltp-fs_bind-tests - pass: 2
- ltp-fs_perms_simple-tests - pass: 19
- ltp-fsx-tests - pass: 2
- ltp-hugetlb-tests - skip: 1, pass: 21
- ltp-io-tests - pass: 3
- ltp-ipc-tests - pass: 9
- ltp-math-tests - pass: 11
- ltp-sched-tests - pass: 14
- ltp-securebits-tests - pass: 4
- ltp-syscalls-tests - skip: 147, pass: 1003
- ltp-timers-tests - skip: 1, pass: 12