stable-rc 4.14.108-rc1/89092dee50e7: no regressions found in project stable v.4.14.y on OE - sanity
Summary ------------------------------------------------------------------------
kernel: 4.14.108-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: 89092dee50e7f804b44bda5e1fb7911bd49a4998 git describe: v4.14.107-132-g89092dee50e7 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe-sanity/build/v4.1...
No regressions (compared to build v4.14.107)
No fixes (compared to build v4.14.107)
Boards, architectures and test suites: -------------------------------------
i386 * boot - pass: 1, * ltp-quickhit-tests - pass: 111,
x15 - arm * boot - pass: 1, * install-android-platform-tools-r2600 - pass: 2, * ltp-quickhit-tests - pass: 110, skip: 1
x86_64 * boot - pass: 1, * ltp-quickhit-tests - pass: 110, skip: 1
Hello!
Just the heads-up that this failed on ARM64 due to: | /srv/oe/build/tmp-lkft-glibc/work-shared/hikey/kernel-source/drivers/clocksource/arm_arch_timer.c:433:4: error: 'const struct arch_timer_erratum_workaround' has no member named 'read_cntpct_el0'; did you mean 'read_cntvct_el0'? | .read_cntpct_el0 = sun50i_a64_read_cntpct_el0, | ^~~~~~~~~~~~~~~ | read_cntvct_el0
Greetings!
Daniel Díaz daniel.diaz@linaro.org
On Wed, 20 Mar 2019 at 15:36, Linaro QA qa-reports@linaro.org wrote:
Summary
kernel: 4.14.108-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.14.y git commit: 89092dee50e7f804b44bda5e1fb7911bd49a4998 git describe: v4.14.107-132-g89092dee50e7 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe-sanity/build/v4.1...
No regressions (compared to build v4.14.107)
No fixes (compared to build v4.14.107)
Boards, architectures and test suites:
i386
- boot - pass: 1,
- ltp-quickhit-tests - pass: 111,
x15 - arm
- boot - pass: 1,
- install-android-platform-tools-r2600 - pass: 2,
- ltp-quickhit-tests - pass: 110, skip: 1
x86_64
- boot - pass: 1,
- ltp-quickhit-tests - pass: 110, skip: 1
-- Linaro QA (BETA) https://qa-reports.linaro.org
On Wed, Mar 20, 2019 at 03:39:41PM -0600, Daniel Díaz wrote:
Hello!
Just the heads-up that this failed on ARM64 due to: | /srv/oe/build/tmp-lkft-glibc/work-shared/hikey/kernel-source/drivers/clocksource/arm_arch_timer.c:433:4: error: 'const struct arch_timer_erratum_workaround' has no member named 'read_cntpct_el0'; did you mean 'read_cntvct_el0'? | .read_cntpct_el0 = sun50i_a64_read_cntpct_el0, | ^~~~~~~~~~~~~~~ | read_cntvct_el0
Thanks, this should be fixed in my next sync.
greg k-h
On Wed, Mar 20, 2019 at 03:39:41PM -0600, Daniel Díaz wrote:
Hello!
Just the heads-up that this failed on ARM64 due to: | /srv/oe/build/tmp-lkft-glibc/work-shared/hikey/kernel-source/drivers/clocksource/arm_arch_timer.c:433:4: error: 'const struct arch_timer_erratum_workaround' has no member named 'read_cntpct_el0'; did you mean 'read_cntvct_el0'? | .read_cntpct_el0 = sun50i_a64_read_cntpct_el0, | ^~~~~~~~~~~~~~~ | read_cntvct_el0
Wait, if it failed, how come this message was returned:
No regressions (compared to build v4.14.107)
Is this the problem where if the build breaks, nothing gets reported?
thanks,
greg k-h
Hello!
On Wed, 20 Mar 2019 at 23:31, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Wed, Mar 20, 2019 at 03:39:41PM -0600, Daniel Díaz wrote:
Hello!
Just the heads-up that this failed on ARM64 due to: | /srv/oe/build/tmp-lkft-glibc/work-shared/hikey/kernel-source/drivers/clocksource/arm_arch_timer.c:433:4: error: 'const struct arch_timer_erratum_workaround' has no member named 'read_cntpct_el0'; did you mean 'read_cntvct_el0'? | .read_cntpct_el0 = sun50i_a64_read_cntpct_el0, | ^~~~~~~~~~~~~~~ | read_cntvct_el0
Wait, if it failed, how come this message was returned:
No regressions (compared to build v4.14.107)
Is this the problem where if the build breaks, nothing gets reported?
Exactly right. Dan added the 'build' status report to mainline builds, but right now it's only being reported for the QEMU devices. Once we iron out those issues we'll add it to stable sanity reports so that we notify about these problems automatically, without pesky humans intervening.
Greetings!
Daniel Díaz daniel.diaz@linaro.org
-
Daniel Díaz -
Greg Kroah-Hartman -
Linaro QA