stable-rc 5.0.18-rc1/a8403b3cf606: regressions detected in project stable v5.0.y on OE - sanity
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,
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 informedi386: build: * build_process
* test src: not informedjuno-r2: build: * build_process
* test src: not informedx15: build: * build_process
* test src: not informedx86: build: * build_process
* test src: not informedNo 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???
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 informedi386: build: * build_process
* test src: not informedjuno-r2: build: * build_process
* test src: not informedx15: build: * build_process
* test src: not informedx86: build: * build_process
* test src: not informedNo 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
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 informedi386: build: * build_process
* test src: not informedjuno-r2: build: * build_process
* test src: not informedx15: build: * build_process
* test src: not informedx86: build: * build_process
* test src: not informedNo 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
On Wed, May 22, 2019 at 08:09:48AM -0500, Dan Rue wrote:
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 informedi386: build: * build_process
* test src: not informedjuno-r2: build: * build_process
* test src: not informedx15: build: * build_process
* test src: not informedx86: build: * build_process
* test src: not informedNo 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.
How are you all mirroring my tree? This looks crazy, you should not be pulling from kernel.org for all builds. Don't you sync locally and then kick everything off which then pulls from that local repo?
We have bad enough bandwidth and cpu usage on git.kernel.org, let's not hurt it by doing pulls for every build from it. Heck, even I have a local mirror :)
thanks,
greg k-h
On Wed, May 22, 2019 at 03:34:51PM +0200, Greg KH wrote:
On Wed, May 22, 2019 at 08:09:48AM -0500, Dan Rue wrote:
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 informedi386: build: * build_process
* test src: not informedjuno-r2: build: * build_process
* test src: not informedx15: build: * build_process
* test src: not informedx86: build: * build_process
* test src: not informedNo 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.
How are you all mirroring my tree? This looks crazy, you should not be pulling from kernel.org for all builds. Don't you sync locally and then kick everything off which then pulls from that local repo?
We have bad enough bandwidth and cpu usage on git.kernel.org, let's not hurt it by doing pulls for every build from it. Heck, even I have a local mirror :)
We have a local cache so it's really not inefficient, it's just a matter of a race condition between the trigger and the checkout.
Incidentally, we're working to change how our builds work to be much closer to kernelci's style of kernel building, so that instead of rebuilding openembedded every time, we're just doing a kernel build.
Dan
-
Dan Rue -
Daniel Díaz -
Greg KH -
Linaro QA