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

On Wed, May 22, 2019 at 07:50:48AM +0200, Greg KH 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???

11:55:50 ERROR: linux-generic-stable-rc-5.0+gitAUTOINC+a8403b3cf6-r0 do_fetch: Fetcher failure: Unable to find revision a8403b3cf60636ef0be2daa710f8515d0a8a0410 in branch linux-5.0.y even from upstream

It looks like you pushed twice? When that happens, it triggers a build but by the time it gets to the git checkout for the rev that triggered the build, it no longer exists. The subsequent push has built cleanly and is being tested now.

Dan