From: ci_notify@linaro.org Date: Thu, 27 Aug 2026 14:30:00 +0000 (UTC) Reply-To: linaro-toolchain@lists.linaro.org
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
My manual investigation process has detected a problem with that conclusion, and ditto.
In aarch64 native, after: | gcc patch https://patchwork.sourceware.org/patch/142242 | Author: Hans-Peter Nilsson hp@axis.com | Date: Wed Aug 26 15:16:16 2026 +0200 | | NOT vs. ROTATE (was: [CRIS PATCH] Support bitreverse32, rotatesi3_16 and other swap variants.) | | > From: Hans-Peter Nilsson hp@axis.com | > Date: Tue, 25 Aug 2026 17:50:01 +0200 | | ... 36 lines of the commit log omitted. | ... applied on top of baseline commit: | d9dcc189896 fortran: array descriptor: Move dtype layout constants out of header [PR122521]
Produces 2 regressions: | | regressions.sum: | Running gcc:gcc.misc-tests/gcov.exp ... | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
That's quite unlikely, as that message was a suggestion for a documentation patch that touched only gcc/doc/md.texi.
I have a hunch gcc.misc-tests/gcov-39.c is flaky, if not generally then at least in the context of your CI. I suggest you consider filtering out that test until your human resources has investigated the flakiness.
Used configuration : *CI config* tcwg_gcc_check aarch64-linux-gnu *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and improvements as well as configure and make commands are in
The list of [ignored] baseline and flaky failures are in
Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/buil... Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/1...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.
brgds, H-P
Yes, I agree with you. Thanks for your investigations.
It is not flaky on the sense that it always gives the same result. That's why our CI couldn't have detected it as flaky. But clearly, this failure seems dependant on a specific CI context.
I m checking this to either fix or filter it out.
Cheers
On Thu, 8 Oct 2026 at 11:17, Hans-Peter Nilsson via linaro-toolchain < linaro-toolchain@lists.linaro.org> wrote:
From: ci_notify@linaro.org Date: Thu, 27 Aug 2026 14:30:00 +0000 (UTC) Reply-To: linaro-toolchain@lists.linaro.org
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please
find some details below.
My manual investigation process has detected a problem with that conclusion, and ditto.
In aarch64 native, after: | gcc patch https://patchwork.sourceware.org/patch/142242 | Author: Hans-Peter Nilsson hp@axis.com | Date: Wed Aug 26 15:16:16 2026 +0200 | | NOT vs. ROTATE (was: [CRIS PATCH] Support bitreverse32,
rotatesi3_16 and other swap variants.)
| | > From: Hans-Peter Nilsson hp@axis.com | > Date: Tue, 25 Aug 2026 17:50:01 +0200 | | ... 36 lines of the commit log omitted. | ... applied on top of baseline commit: | d9dcc189896 fortran: array descriptor: Move dtype layout constants
out of header [PR122521]
Produces 2 regressions: | | regressions.sum: | Running gcc:gcc.misc-tests/gcov.exp ... | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in
branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
| FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths,
was 1/7
That's quite unlikely, as that message was a suggestion for a documentation patch that touched only gcc/doc/md.texi.
I have a hunch gcc.misc-tests/gcov-39.c is flaky, if not generally then at least in the context of your CI. I suggest you consider filtering out that test until your human resources has investigated the flakiness.
Used configuration : *CI config* tcwg_gcc_check aarch64-linux-gnu *configure and test flags:* none, autodetected on
aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
If you have any questions regarding this report, please ask on
linaro-toolchain@lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways
to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/buil...
The full lists of regressions and improvements as well as configure and
make commands are in
http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/buil...
The list of [ignored] baseline and flaky failures are in
http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/buil...
Current build :
http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/buil...
Reference build :
http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/1...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.
brgds, H-P _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-leave@lists.linaro.org
linaro-toolchain@lists.linaro.org