Re: stable-rc 5.0.18-rc1/a8403b3cf606: regressions detected in project stable v5.0.y on OE - sanity

Hello!

On Wed, 22 May 2019 at 00:50, Greg KH gregkh@linuxfoundation.org wrote:

On Tue, May 21, 2019 at 06:56:07PM +0000, Linaro QA wrote:

...

Summary

kernel: 5.0.18-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-5.0.y git commit: a8403b3cf60636ef0be2daa710f8515d0a8a0410 git describe: v5.0.17-121-ga8403b3cf606 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.0-oe-sanity/build/v5.0....

Regressions (compared to build v5.0.17-124-gbb2772791a81)

dragonboard-410c: build: * build_process

* test src: not informed

i386: build: * build_process

* test src: not informed

juno-r2: build: * build_process

* test src: not informed

x15: build: * build_process

* test src: not informed

x86: build: * build_process

* test src: not informed

No fixes (compared to build v5.0.17-124-gbb2772791a81)

Boards, architectures and test suites:

dragonboard-410c

• build - fail: 1,

i386

• build - fail: 1,

juno-r2

• build - fail: 1,

x15

• build - fail: 1,

x86

• build - fail: 1,

Everything failed to build???

Yes, because the build was triggered by a8403b3cf60636ef0be2daa710f8515d0a8a0410, which later got replaced by 5eaa7ad66ec7e9d1c3e1ef871ec29a5427d05ca7 (force push), it was not possible to git-fetch the original revision from the branch.

Naresh has now shared results for 5eaa7ad66ec7, which went great.

Greetings!

Daniel Díaz daniel.diaz@linaro.org