Hi,
These tests are incorrect. Therefore, we will correct them.
The lastprivate variables pa/pb did not meet OpenMP's requirements because they were treated as private instead of the required shared variable type.
Please ignore the mail. We'll update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信日時: 2026年7月7日 21:06
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; safonsof(a)amd.com <safonsof(a)amd.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-21388-g154834916515: 2 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
| commit llvmorg-23-init-21388-g154834916515
| Author: Sergio Afonso <safonsof(a)amd.com>
| Date: Wed Jul 1 16:54:06 2026 +0100
|
| [Flang][OpenMP][MLIR] Improve SPMD-No-Loop handling (#206953)
|
| This patch modifies the handling of the
| `-fopenmp-assume-teams-oversubscription` and
| `-fopenmp-assume-threads-oversubscription` compiler options in Flang and
| ... 13 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0688 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0688/Fujitsu-Fortran-0688_0014.test
| NOEXE: test-suite :: Fujitsu/Fortran/0688/Fujitsu-Fortran-0688_0016.test
| # "NOEXE" means : the test program cannot be compiled
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2242. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)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_flang_test--main-aarch64-O3-neoverse_v1…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/154834916515ad8f9286a759a4f629f…
Hi,
These tests are incorrect. Therefore, we will correct them.
The test incorrectly uses statement function dummy argument names (e.g., a, b) that conflict with already declared array variables in the same scope.
Please ignore the mail. We'll update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信: 2026 年 7 月 9 日 (木曜日) 5:14
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; kwyatt.external(a)hpe.com <kwyatt.external(a)hpe.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-21399-gb1b919870974: 2 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O0-debug, after:
| commit llvmorg-23-init-21399-gb1b919870974
| Author: kwyatt-ext <kwyatt.external(a)hpe.com>
| Date: Wed Jul 1 11:35:28 2026 -0500
|
| [flang] Implement check for statement function dummy argument names (#204417)
|
| Implement F2023 19.4.2 conformance check for statement function dummy
| argument names
|
| ... 16 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0289 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0289/Fujitsu-Fortran-0289_0025.test
| Running test-suite:Fujitsu/Fortran/0572 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0572/Fujitsu-Fortran-0572_0463.test
| # "NOEXE" means : the test program cannot be compiled
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2243. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)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_flang_test--main-aarch64-O0-debug-build…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/b1b9198709749eb612bfce7cfb6a3ab…
Hi,
These tests are incorrect. Therefore, we will correct them.
The tests fail after a change in Flang runtime allocation behavior from malloc to 64-byte aligned aligned_alloc.
Please ignore the mail. We'll update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信: 2026 年 7 月 4 日 (土曜日) 14:21
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: jason.van-beusekom(a)hpe.com <jason.van-beusekom(a)hpe.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-23-init-21381-ga675a661b86f: 9 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
| commit llvmorg-23-init-21381-ga675a661b86f
| Author: Jason Van Beusekom <jason.van-beusekom(a)hpe.com>
| Date: Wed Jul 1 10:36:38 2026 -0500
|
| [Flang-RT] Change alignment for allocatable and pointer arrays to 64 … (#206525)
|
| …bytes
|
| in https://github.com/llvm/llvm-project/pull/194969 the default array
| ... 9 lines of the commit log omitted.
Produces 9 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0449 ...
| FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0005.test
| FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0006.test
| FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0009.test
| FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0082.test
| ... and 6 more
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2240. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)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_flang_test--main-aarch64-O3-neoverse_v1…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/a675a661b86f54d45e90778362a97c1…
Hi,
The test violates Fortran dummy argument aliasing rules.
Overlapping elements (xx(6) and yy(1)) reference the same memory (x(6)), and the code performs both read and write through different dummy arguments, resulting in undefined behavior.
Please ignore the mail. We'll update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信: 2026 年 7 月 5 日 (日曜日) 21:01
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; kunalspathak.github(a)gmail.com <kunalspathak.github(a)gmail.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-20398-g2668971e1421: 1 regression on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vla, after:
| commit llvmorg-23-init-20398-g2668971e1421
| Author: Kunal Pathak <kunalspathak.github(a)gmail.com>
| Date: Wed Jun 24 08:22:51 2026 -0700
|
| [AArch64][ISel] Enable profile-aware branch condition merging (#201486)
|
| AArch64 previously inherited the default {-1, -1, -1} for
| `getJumpConditionMergingParams`, causing
| `shouldKeepJumpConditionsTogether` in SelectionDAGBuilder to always
| ... 28 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0328 ...
| FAIL: test-suite :: Fujitsu/Fortran/0328/Fujitsu-Fortran-0328_0022.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2241. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)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_flang_test--main-aarch64-Ofast-sve_vla-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/2668971e14219205ddf6b1f753cf83f…
On 7/4/26 18:40, ci_notify(a)linaro.org wrote:
> /usr/bin/ld: error: libcommon.a: file too short
I don't understand this. How can any patch to the Fortran front end
(much less a completely trivial one) affect libcommon.a? If that file
was truncated maybe it was a transient disk-full or file system error?
-Sandra
On 05/07/2026 02:18, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In simplebootstrap_build master-aarch64-bootstrap, after:
> | 7 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/138418
> | 9535bc30d4a [PATCH v3 7/8] MAINTAINERS: generate from MAINTAINERS.yml
> | 4a13feeed49 [PATCH v3 6/8] MAINTAINERS.yml: Add libcpp to all C and C++ maintainer's roles
> | 246b6c1ec06 [PATCH v3 5/8] MAINTAINERS.yml: Handle libgrust explicitly
> | 024b571b710 [PATCH v3 4/8] MAINTAINERS.yml: Restore James Norris' email address
> | f13d5705819 [PATCH v3 3/8] MAINTAINERS.yml: Correct Martin Liška's name
> | ... and 2 more patches in gcc
> | ... applied on top of baseline commit:
> | e365e5473a8 libgcc, Darwin: Fix missing prerequisite [PR123976].
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> | # First few build errors in logs:
> | # 01:34:20 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:34:20 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:42:17 make[8]: [Makefile:868: stamp-modules-bits] Error 1 (ignored)
> | # 02:02:57 make[3]: *** [Makefile:4629: io/intrinsics.lo] Error 1
> | # 02:02:57 make[2]: *** [Makefile:1882: all] Error 2
> | # 02:02:57 make[1]: *** [Makefile:21363: all-target-libgfortran] Error 2
> | # 02:02:57 make: *** [Makefile:1142: all] Error 2
> |
This report is also bogus. The patch doesn't go anywhere near the main compiler or library sources.
R.
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)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
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 04/07/2026 04:12, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In simplebootstrap_build master-aarch64-bootstrap, after:
> | 8 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/138422
> | 16c863d8c02 [PATCH v3 8/8] MAINTAINERS: Add a script to create a new entry in the mainainers data
> | ff60e686f8f [PATCH v3 7/8] MAINTAINERS: generate from MAINTAINERS.yml
> | d3f4eba32fd [PATCH v3 6/8] MAINTAINERS.yml: Add libcpp to all C and C++ maintainer's roles
> | 403583056ec [PATCH v3 5/8] MAINTAINERS.yml: Handle libgrust explicitly
> | 3389564de59 [PATCH v3 4/8] MAINTAINERS.yml: Restore James Norris' email address
> | ... and 3 more patches in gcc
> | ... applied on top of baseline commit:
> | a20f4528f3a tree-optimization/122569 - recognize CLZ via isolated MSB DeBruijn lookup
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> | # First few build errors in logs:
> | # 00:09:12 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 00:09:12 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 00:59:19 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 00:59:19 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:16:13 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:16:13 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:17:22 make[6]: *** [Makefile:631: libstdc++fsconvenience.la] Error 1
> | # 01:17:22 make[6]: *** [Makefile:628: libstdc++fs.la] Error 1
> | # 01:17:22 make[5]: *** [Makefile:802: all-recursive] Error 1
> | # 01:17:22 make[4]: *** [Makefile:580: all-recursive] Error 1
> |
Nothing in this patch could possibly produce the above error, so it must be due to the baseline commit being broken, or some other problem with the CI bot.
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)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
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
This doesn't seem right given the patch. All tests passed when I tested it locally on aarch64 using two different toolchains.
________________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: 05 July 2026 12:02 PM
To: Yury Khrustalev
Cc: Yury Khrustalev
Subject: [Linaro-TCWG-CI] glibc patch #138079: 2 regressions 97 fixes on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_check master-aarch64, after:
| glibc patch https://patchwork.sourceware.org/patch/138079
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Mon Jun 29 17:37:22 2026 +0100
|
| [PATCH 1/1] aarch64: compile malloc ifuncs conditionally
|
| On AArch64, ifuncs are used for malloc functions by default.
|
| The code for resolvers in sysdeps/aarch64/multiarch/malloc-ifuncs.c
| ... 5 lines of the commit log omitted.
| ... applied on top of baseline commit:
| d109f366ce build-many-glibcs.py: Update Linux kernel version to 7.1
Produces 2 regressions 97 fixes:
|
| regressions.sum:
| Running glibc:nptl ...
| FAIL: nptl/tst-fopen-threaded
| Running glibc:posix ...
| FAIL: posix/tst-affinity-static
|
| fixes.sum:
| Running glibc:debug ...
| FAIL: debug/tst-fortify-syslog
| Running glibc:dirent ...
| FAIL: dirent/tst-readdir-long
| ... and 108 more
Used configuration :
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
If you have any questions regarding this report, please ask on linaro-toolchain(a)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_glibc_check--master-aarch64-precommit/b…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-build/build…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.