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.
Thanks for reporting this.
This is expected regression due to possible bug in Valgrind. For details, see:
https://bugs.kde.org/show_bug.cgi?id=522497https://inbox.sourceware.org/libc-alpha/cover.1782766548.git.fweimer@redhat…
Thanks,
Yury
________________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: 05 July 2026 10:50 AM
To: Yury Khrustalev
Cc: Yury Khrustalev
Subject: [Linaro-TCWG-CI] glibc patch #138207: 1 regression 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/138207
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Wed Jul 1 14:16:17 2026 +0100
|
| [PATCH] aarch64: Fail early if malloc ifunc resolver is called incorrectly
|
| This patch adds simple check that validates the call to ifunc resolver
| for the malloc function. If resolver is called correctly, it must
| receive at least 1 argument that is equal to the value of AT_HWCAP
| ... 6 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 1 regression 97 fixes:
|
| regressions.sum:
| Running glibc:elf ...
| FAIL: elf/tst-valgrind-smoke
|
| fixes.sum:
| Running glibc:debug ...
| FAIL: debug/tst-fortify-syslog
| ... and 110 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.
On Thu, 2 Jul 2026 at 23:45, <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 arm-eabi cortex-m33 hard, after:
> | commit gcc-17-1905-g70e630b6d29b
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Jun 25 12:59:04 2026 +0100
> |
> | libstdc++: Update feature test macros and tests for C++29
> |
> | With r17-1595-g0c5c6249a2e9a7 G++ supports -std=c++29 so update our
> | feature test macro generation and testsuite to know about it.
> |
> | ... 19 lines of the commit log omitted.
>
> Produces 5 regressions 5 fixes:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++29 execution test
> | FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++29 execution test
> | FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++29 execution test
> | FAIL: 27_io/print/2.cc -std=gnu++29 (test for excess errors)
> | ... and 1 more
> |
> | fixes.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++26 execution test
> | FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++26 execution test
> | FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++26 execution test
> | FAIL: 27_io/print/2.cc -std=gnu++26 (test for excess errors)
> | ... and 1 more
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m33 --with-float=hard --target_board=-mthumb/-march=armv8-m.main+dsp+fp/-mtune=cortex-m33/-mfloat-abi=hard/-mfpu=auto qemu-cpu=cortex-m33
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1942. (Require Linaro login) Please let us know if you have a fix.
This isn't really a regression, it's because the tests switched from
being run with -std=gnu++26 to -std=gnu++29, but they still FAIL the
same way.
>
> 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_gnu_embed_check_gcc--master-thumb_m33_h…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h…
>
> Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
I think this is a misattribution of the failure. #203481 is a change
of the CMake build system, it does not change anything functional in
the flang compiler. #203481 had a build problem which was fixed in
#204438. But since Flang built successfully, it cannot be the problem
of that CI problem.
Michael
Am Fr., 19. Juni 2026 um 13:56 Uhr schrieb <ci_notify(a)linaro.org>:
>
> 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-19659-g3fee6e5ab45d
> | Author: Michael Kruse <llvm-project(a)meinersbur.de>
> | Date: Wed Jun 17 16:13:40 2026 +0200
> |
> | [Flang] Add mock flang driver (#203481)
> |
> | Add a mock driver to pass CMake's compiler introspection for
> | CMake_Fortran_COMPILER. It's purpose is to not having to build the full
> | flang compiler for the runtimes-configure phase in
> | ... 59 lines of the commit log omitted.
>
> Produces 18533 regressions:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0004 ...
> | NOEXE: test-suite :: Fujitsu/Fortran/0004/Fujitsu-Fortran-0004_0001.test
> | NOEXE: test-suite :: Fujitsu/Fortran/0004/Fujitsu-Fortran-0004_0002.test
> | Running test-suite:Fujitsu/Fortran/0005 ...
> | NOEXE: test-suite :: Fujitsu/Fortran/0005/Fujitsu-Fortran-0005_0001.test
> | ... and 19173 more
> | # "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-2235. (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/3fee6e5ab45d1d352f995ae4eafa510…
--
Tardyzentrismus verboten!
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In aarch64 native, after:
| commit glibc-2.43.9000-403-g9ed3576e61f
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Tue May 26 11:19:53 2026 +0100
|
| malloc: aarch64: Add ifuncs for malloc functions
|
| Introduce ifuncs and resolvers for functions pertinent to the
| malloc interface on the AArch64 target: malloc, calloc, free,
| realloc, memalign, valloc, pvalloc, posix_memalign, aligned_alloc,
| ... 13 lines of the commit log omitted.
Produces 118 regressions:
|
| regressions.sum:
| Running gdb:gdb.base/call-strs.exp ...
| FAIL: gdb.base/call-strs.exp: call str_func("a","b","c","d","e","f","g")
| FAIL: gdb.base/call-strs.exp: print str_func("a","b","c","d","e","f","g")
| Running gdb:gdb.base/callfuncs.exp ...
| FAIL: gdb.base/callfuncs.exp: noproto: p t_char_array_values("carray 1","carray 2")
| ... and 125 more
Used configuration :
*CI config* tcwg_gnu_native_check_gdb 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
We track this bug report under https://linaro.atlassian.net/browse/GNU-1934. (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_gnu_native_check_gdb--master-aarch64-bu…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=9ed3576e61f7a87eb83d…