Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_build/main-aarch64, after:
| commit llvmorg-22-init-2744-ga15b629527a9
| Author: Jon Roelofs <jonathan_roelofs(a)apple.com>
| Date: Tue Aug 5 17:08:00 2025 -0700
|
| Revert "Strip the full path from __FILE__ in the LDBG macro and keep only the filename (#150677)"
|
| This reverts commit 5d26e3c227f4b4a1761a8b0001b3165198def479.
|
| It breaks the modules build of clang, since every source file has a different
| ... 9 lines of the commit log omitted.
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_llvm -- clang;lld;flang;clang-tools-extra openmp :
| # FAILED
| # First few build errors in logs:
| # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:71:12: error: a type specifier is required for all declarations
| # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:77:4: error: identifier 'raw_ldbg_ostream' after '~' in destructor name does not name a type
| # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:54:9: error: member initializer 'os' does not name a non-static data member or base class
| # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:59:23: error: use of undeclared identifier 'os'
| # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:61:12: error: use of undeclared identifier 'os'
| # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:73:7: error: only constructors take base initializers
| # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:75:5: error: use of undeclared identifier 'SetUnbuffered'
| # 00:03:30 ../llvm/mlir/lib/IR/PatternLoggingListener.cpp:10:3: error: use of undeclared identifier '_GET_LDBG_MACRO'
| # 00:03:30 ../llvm/mlir/lib/IR/PatternLoggingListener.cpp:17:3: error: use of undeclared identifier '_GET_LDBG_MACRO'
| # 00:03:30 ../llvm/mlir/lib/IR/PatternLoggingListener.cpp:24:3: error: use of undeclared identifier '_GET_LDBG_MACRO'
|
| From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_llvm -- clang;lld;flang;clang-tools-extra openmp :
| 1
Used configuration :
tcwg_flang_build/main-aarch64
We track this bug report under https://linaro.atlassian.net/browse/LLVM-1738. 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
* https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/5111/artifac…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/5111/artifac…
Current build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/5111/artifac…
Reference build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/5108/artifac…
Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha…
Full commit : https://github.com/llvm/llvm-project/commit/a15b629527a975ec592c95d69d04ef3…
[This is a CI regression report that wasn't sent due to infra problem.]
Hi Florian,
Your glibc patch fixes a lot of failures in GDB testsuite, but also creates a few new FAILs -- are these expected?
Thanks!
===
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-aarch64, after:
| commit glibc-2.41.9000-556-g620f0730f31
| Author: Florian Weimer <fweimer(a)redhat.com>
| Date: Mon Jul 28 14:16:52 2025 +0200
|
| elf: Compile _dl_debug_state separately (bug 33224)
|
| This ensures that the compiler will not inline it, so that
| debuggers which do not use the Systemtap probes can reliably
| set a breakpoint on it.
| ... 3 lines of the commit log omitted.
Produces 8 regressions 1564 fixes:
|
| regressions.sum:
| Running gdb:gdb.dap/cxx-exception.exp ...
| FAIL: gdb.dap/cxx-exception.exp: exceptions in log file
| Running gdb:gdb.dap/ptrref.exp ...
| FAIL: gdb.dap/ptrref.exp: exceptions in log file
| Running gdb:gdb.threads/process-dies-while-detaching.exp ...
| ... and 7 more
|
| fixes.sum:
| Running gdb:gdb.arch/aarch64-sve-sigunwind.exp ...
| FAIL: gdb.arch/aarch64-sve-sigunwind.exp: $\z2.b.u contents were correctly unwound
| FAIL: gdb.arch/aarch64-sve-sigunwind.exp: size of $\z3.b.u was correctly unwound
| FAIL: gdb.arch/aarch64-sve-sigunwind.exp: $\z12.b.u contents were correctly unwound
| FAIL: gdb.arch/aarch64-sve-sigunwind.exp: $\z22.b.u contents were correctly unwound
| ... and 1676 more
Used configuration :
*CI config* tcwg_gnu_native_check_gdb master-aarch64
*configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
We track this bug report under https://linaro.atlassian.net/browse/GNU-692. 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
* https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/glibc/sh…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=620f0730f311635cd0e1…
--
Maxim Kuvyrkov
https://www.linaro.org
Dear Linaro Community,
I am looking for advice on how to reproduce a flang-arm64-windows-msvc LLVM build bot failure (hopefully I ended up in the right place here).
I had to revert an LLVM PR (https://github.com/llvm/llvm-project/pull/150783) that broke the flang-arm64-windows-msvc LLVM buildbot yesterday due to some tablegen-related problem. I did prepare a reland PR (https://github.com/llvm/llvm-project/pull/151125) that addresses a potential issue. However, since I did not see any other buildbot failures and since I was not able to reproduce the problem locally, I wonder if there is a way to run the flang-arm64-windows-msvc buildbot on my reland PR? Alternatively, hints on how to reproduce the problem locally on a x86 Linux machine would be appreciated.
Best,
Tobias
Hello Tom,
ci_notify(a)linaro.org writes:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details
> below.
>
> In gdb_check master-arm, after:
> | 9 patches in gdb
> | Patchwork URL: https://patchwork.sourceware.org/patch/117104
> | 02107b8252d [PATCH 9/9] [gdb/testsuite] Add gdb.tui/tui-mode-switch.exp
> | 74b2f1eb572 [PATCH 8/9] [gdb/testsuite] Add Term::with_term
> | 6f3e219e902 [PATCH 7/9] [gdb/testsuite] Add Term::_esc_0x3d and Term::_esc_0x3e
> | 9d1466d5f3f [PATCH 6/9] [gdb/testsuite] Add Term::_esc_0x28_B and Term::_esc_0x28_0
> | 2c51f81639a [PATCH 5/9] [gdb/testsuite] Add Term::_csi_r
> | ... and 4 more patches in gdb
> | ... applied on top of baseline commit:
> | 0937ed3f050 Add forgotten ChangeLog entry for commit
> | 7c1c13e896c76879bcf3fb29332e0a59918bc9e0.
>
> Produces 23 regressions 3 fixes:
<snip>
> Current build :
> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/5001/artifac…
> Reference build :
> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3017/artifact/ar…
This is a false positive. We're currently moving our CI jobs to another
machine (of a different kind, even) and the reference build ran on the
new machine while the build with the patches ran on the old one. Sorry
for the noise.
--
Thiago
Hello Tom,
ci_notify(a)linaro.org writes:
> In gdb_check master-arm, after:
> | 3 patches in gdb
> | Patchwork URL: https://patchwork.sourceware.org/patch/117137
> | a05322508b7 [PATCH 3/3] Require Tcl 8.6.2
> | 2b7dc482e23 [PATCH 2/3] Rewrite tcl_version_at_least
> | a88c3d9f501 [PATCH 1/3] Require Tcl 8.5
> | ... applied on top of baseline commit:
> | 0937ed3f050 Add forgotten ChangeLog entry for commit
> | 7c1c13e896c76879bcf3fb29332e0a59918bc9e0.
>
> Produces 23 regressions 3 fixes:
<snip>
> Current build :
> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/5004/artifac…
> Reference build :
> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3017/artifact/ar…
This is a false positive. We're currently moving our CI jobs to another
machine (of a different kind, even) and the reference build ran on the
new machine while the build with the patches ran on the old one. The
same happened with the other patch about which we notified you today.
Sorry for the noise.
--
Thiago
Hello,
ci_notify(a)linaro.org writes:
> In gdb_check master-arm, after:
> | gdb patch https://patchwork.sourceware.org/patch/117052
> | Author: Aria Nolan <aria(a)chytrid.org>
> | Date: Sat Jul 26 18:44:40 2025 -0600
> |
> | [PATCH] gdb: turn off completions for the inferior command
> |
> | The inferior command takes an inferior ID as an argument. The current
> | completer for the command offers symbols. This patch removes the completion,
> | since the IDs are sequential so it makes little sense to offer that.
> | ... 2 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 0937ed3f050 Add forgotten ChangeLog entry for commit
> | 7c1c13e896c76879bcf3fb29332e0a59918bc9e0.
>
> Produces 23 regressions 3 fixes:
<snip>
> Current build :
> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/5000/artifac…
> Reference build :
> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3017/artifact/ar…
This is a false positive. We're currently moving our CI jobs to another
machine (of a different kind, even) and the reference build ran on the
new machine while the build with the patch ran on the old one. Sorry for
the noise.
--
Thiago
Hi Nathan,
Sorry this report is incorrect because we are in the process of moving
to new machines.
Please ignore it.
Sorry for the noise.
Thanks,
Christophe
On Tue, 29 Jul 2025 at 04:34, <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 gcc_check master-aarch64, after:
> | gcc patch https://patchwork.sourceware.org/patch/117089
> | Author: Nathan Myers <ncm(a)cantrip.org>
> | Date: Mon Jul 28 05:25:55 2025 -0400
> |
> | [PATCHv5] libstdc++: Add NTTP bind_front, -back, not_fn (P2714) [PR119744]
> |
> | Stabilizing.
> |
> | Changes in v5:
> | ... 39 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | a51bf9e10182 ifcvt: Fix ifcvt for multiple phi nodes after factoring operator [PR121236]
>
> Produces 84 regressions 2 fixes:
> |
> | regressions.sum:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/cpp1z/pr85569.C -std=c++20 (test for excess errors)
> | Running g++:g++.dg/modules/modules.exp ...
> | FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (internal compiler error: canonical types differ for identical types 'auto' and 'auto')
> | FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors)
> | ... and 83 more
> |
> | fixes.sum:
> | Running g++:g++.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test
> | Running gcc:gcc.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test
>
> Used configuration :
> *CI config* tcwg_gcc_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
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11852/ar…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11852/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11852/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11852/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4055/artifac…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi Richard,
Sorry this report is incorrect because we are in the process of moving
to new machines.
Please ignore it.
Sorry for the noise.
Thanks,
Christophe
On Tue, 29 Jul 2025 at 04:11, <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 gcc_check master-aarch64, after:
> | gcc patch https://patchwork.sourceware.org/patch/117090
> | Author: Richard Biener <rguenther(a)suse.de>
> | Date: Mon Jul 28 11:36:06 2025 +0200
> |
> | [PATCH] Remove STMT_VINFO_MEMORY_ACCESS_TYPE
> |
> | This should be present only on SLP nodes now. The RISC-V changes
> | are mechanical along the line of the SLP_TREE_TYPE changes.
> |
> | ... 19 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | a51bf9e1018 ifcvt: Fix ifcvt for multiple phi nodes after factoring operator [PR121236]
>
> Produces 6976 regressions 2 fixes:
> |
> | regressions.sum:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/opt/pr112374.C -std=gnu++11 (internal compiler error: Segmentation fault)
> | FAIL: g++.dg/opt/pr112374.C -std=gnu++11 (test for excess errors)
> | FAIL: g++.dg/opt/pr112374.C -std=gnu++17 (internal compiler error: Segmentation fault)
> | FAIL: g++.dg/opt/pr112374.C -std=gnu++17 (test for excess errors)
> | ... and 6984 more
> |
> | fixes.sum:
> | Running g++:g++.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test
> | Running gcc:gcc.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test
>
> Used configuration :
> *CI config* tcwg_gcc_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
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11853/ar…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11853/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11853/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11853/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4055/artifac…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
On Thu, Jul 24, 2025 at 10:42:41AM +0000, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
It appears that this build was running tests on qemu that doesn't seem to support
the same signal handling behaviour for SME as would the kernel that supports SME.
On a system that supports SME with kernel 6.16 these tests work as expected provided
that their dependencies are resolved by dynamic loader to the new version of libgcc.
So, no issue in the patch or in the tests.
Thanks,
Yury
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.
> Our automatic CI has detected problems related to your patch(es).
Thanks, I'm looking into it.
Kind regards,
Yury
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.