linaro-toolchain

linaro-toolchain@lists.linaro.org

4 participants
5772 discussions

Re: [Linaro-TCWG-CI] llvmorg-23-init-20756-gd445267fbb56: 2 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, The tests are incorrect. The causes are as follows. The test programs perform an exact comparison of a single-precision floating-point result. Because it is compiled with -msve-vector-bits=scalable, the generated code adapts to the SVE vector length of the execution environment. As a result, the composition of partial sums and the order of floating-point additions vary between systems, producing different rounding results. The tests failed because it did not allow normal floating-point rounding differences caused by vectorized execution and compared the result against specific values using exact equality. Please ignore the mail. We'll update the tests. 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 月 14 日 (火曜日) 9:53 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> Cc: david.green(a)arm.com <david.green(a)arm.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> 件名: [Linaro-TCWG-CI] llvmorg-23-init-20756-gd445267fbb56: 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-Ofast-sve_vla, after: | commit llvmorg-23-init-20756-gd445267fbb56 | Author: David Green <david.green(a)arm.com> | Date: Fri Jun 26 15:54:41 2026 +0100 | | [AArch64] Increase the max interleave factor to 4 for loops with reductions (#205612) | | The default max interleave factor is 2. Increasing it to 4 universally | can spend an amount of codeside on something that does not always | increase performance (especially if the loop gets over-unrolled). Small | ... 5 lines of the commit log omitted. Produces 2 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0366 ... | FAIL: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0002.test | FAIL: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0098.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-2247. (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/d445267fbb569e67ba9311f8c2bc675…

2 weeks, 5 days

Re: [Linaro-TCWG-CI] glibc patch #139350: 1 regression 111 fixes on arm

by Artem Proskurnev

Hello! The single regression reported by Linaro TCWG CI on both aarch64 and arm is XPASS: nptl/tst-create4. This test is intentionally marked XFAIL in the patch (test-xfail-tst-create4 = yes) because it verifies the non-interleave property that this patch deliberately removes: with the patch, constructors of independent DSOs loaded from different threads can interleave. An XPASS on some runs is expected flaky behaviour for a test that documents a removed property; it does not indicate a real regression. No PASS->FAIL transitions are reported on either architecture. The 97/111 ‘fixes’ are environment-driven (no cgroupv2, no /dev/fuse, no root in CI container). An x86_64 make check run under identical conditions on both sides shows 0 patch-attributable transitions. > A third test, tst-create4/tst-create4mod-a/tst-create4mod-b, > documents a property that the patch removes: under the pre-BZ-15686 > locking model, dl_load_lock serialised the entire _dl_open across > threads, so constructors of independent DSOs loaded from different > threads could not interleave. After the patch, they can. The test > asserts the OLD non-interleaving behaviour and is therefore marked > XFAIL via test-xfail-tst-create4 = yes. It is included as a > diagnostic tool for downstream applications that may have implicitly > relied on the old total order -- plugin registries whose registration > order determined behaviour, signal-handler chains installed in > constructors, global logger/telemetry setup, etc. Thanks! 17.07.2026 23:53, ci_notify(a)linaro.org: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In glibc_check master-arm, after: > | glibc patchhttps://patchwork.sourceware.org/patch/139350 > | Author: Artem Proskurnev<temap(a)mail.ru> > | Date: Thu Jul 16 19:04:01 2026 +0300 > | > | [PATCH v3] elf: Release dl_load_lock before running dlopen constructors (BZ 15686) > | > | This addresses one instance of the long-standing class of deadlocks > | described in BZ #15686: ELF constructors and destructors invoked by > | the dynamic loader run with dl_load_lock held, so any code path in > | ... 232 lines of the commit log omitted. > | ... applied on top of baseline commit: > | a29c483d3c Add RWF_NOSIGNAL from Linux 6.18 to bits/uio-ext.h > > Produces 1 regression 111 fixes: > | > | regressions.sum: > | Running glibc:nptl ... > | XPASS: nptl/tst-create4 > | > | fixes.sum: > | Running glibc:debug ... > | FAIL: debug/tst-fortify-syslog > | ... and 125 more > > Used configuration : > *CI config* tcwg_glibc_check master-arm > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > If you have any questions regarding this report, please ask onlinaro-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-arm-precommit/builds/10367/archive/artifacts/artifacts.precommit/00-sumfiles/ > 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-arm-precommit/builds/10367/archive/artifacts/artifacts.precommit/notify/ > The list of [ignored] baseline and flaky failures are in > *http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/builds/10367/archive/artifacts/artifacts.precommit/sumfiles/xfails.xfail > > Current build :http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/builds/10367/archive/artifacts/ > Reference build :http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10332/archive/artifacts/ > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

3 weeks, 2 days

[committed] Fix signed char test assumption [Was Re: [Linaro-TCWG-CI] gcc-17-2261-g649b2a6d9f9f: 7 regressions on arm]

by Jeffrey Law

On 7/9/2026 4:56 PM, 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 armv8l-unknown-linux-gnueabihf native, after: > | commit gcc-17-2261-g649b2a6d9f9f > | Author: Jeff Law <jeffrey.law(a)oss.qualcomm.com> > | Date: Wed Jul 8 12:30:56 2026 -0600 > | > | [PR rtl-optimization/126136] Fix dest = cond ? x : -1 when STORE_FLAG_VALUE is -1 > | > | So a while back I added support for selecting x/-1 into the ifcvt.cc by using > | scc and a couple ALU operations. That code explicitly rejects STORE_FLAG_VALUE > | if it is not 1 or -1. > | ... 20 lines of the commit log omitted. > > Produces 7 regressions: > | > | regressions.sum: > | Running gcc:gcc.dg/torture/dg-torture.exp ... > | FAIL: gcc.dg/torture/pr126136.c -O0 execution test > | FAIL: gcc.dg/torture/pr126136.c -O1 execution test > | FAIL: gcc.dg/torture/pr126136.c -O2 execution test > | FAIL: gcc.dg/torture/pr126136.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test > | ... and 3 more > > Used configuration : > *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a --with-fpu=neon-fp-armv8 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1959. (Require Linaro login) Please let us know if you have a fix. As others noted, this is a case where the test assumed signed chars. The patch makes the signedness explicit. Bootstrapped and regression tested on armv7 and verified the test now passes on that platform. Pushing to the trunk. jeff

3 weeks, 3 days

Re: [Linaro-TCWG-CI] gcc-17-2325-g4302e16581b4: 10 regressions on arm

by Andrea Pinski

On Wed, Jul 15, 2026 at 10:10 AM <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 armv8l-unknown-linux-gnueabihf native, after: > | commit gcc-17-2325-g4302e16581b4 > | Author: Andrew Pinski <andrew.pinski(a)oss.qualcomm.com> > | Date: Fri Jul 10 16:55:19 2026 -0700 > | > | vect: Add back testcases for trapping math with comparisons [PR36190] > | > | These were originally renamed to no-trapping-math-vect-*.c in r0-87196-g04b03edb56633f > | but were fixed in r0-107313-gf9613c9a919462 but never added back to the > | trapping versions. > | ... 17 lines of the commit log omitted. > > Produces 10 regressions: > | > | regressions.sum: > | Running gcc:gcc.dg/vect/vect.exp ... > | FAIL: gcc.dg/vect/vect-111.c (test for excess errors) > | FAIL: gcc.dg/vect/vect-111.c -flto -ffat-lto-objects (test for excess errors) > | FAIL: gcc.dg/vect/vect-ifcvt-12.c (test for excess errors) > | FAIL: gcc.dg/vect/vect-ifcvt-12.c -flto -ffat-lto-objects (test for excess errors) > | ... and 6 more FAIL: gcc.dg/vect/vect-111.c (test for excess errors) Excess errors: cc1: warning: '-fassociative-math' disabled; other options take precedence This is caused by an interaction with -ftrapping-math added by the new testcases and this from check_vect_support_and_set_flags: ``` } elseif [is-effective-target arm_neon_ok] { eval lappend DEFAULT_VECTCFLAGS [add_options_for_arm_neon ""] # NEON does not support denormals, so is not used for vectorization by # default to avoid loss of precision. We must pass -ffast-math to test # vectorization of float operations. lappend DEFAULT_VECTCFLAGS "-ffast-math" if [is-effective-target arm_neon_hw] { set dg-do-what-default run } else { set dg-do-what-default compile } ``` I am not sure what the best way of solving this. Do we just not test these testcases on arm neon? or something else? > > Used configuration : > *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a --with-fpu=neon-fp-armv8 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1969. (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_gcc_check--master-arm-build/builds/1042… > 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-arm-build/builds/1042… > The list of [ignored] baseline and flaky failures are in > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1042… > > Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1042… > Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1042… > > 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

3 weeks, 4 days

Re: [Linaro-TCWG-CI] gcc-17-2060-gf7cde200320e: 6 regressions on aarch64

by Tomasz Kaminski

On Tue, Jul 14, 2026 at 10:36 PM <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 aarch64 native, after: > | commit gcc-17-2060-gf7cde200320e > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Tue Jun 30 09:46:07 2026 +0200 > | > | libstdc++: Cascade wall-time saves in lazy expansion seeding > [PR124853] > | > | When _M_get_sys_info seeds a Zone line by looking up the active > rule > | just before info.begin, the previous code interpreted each rule in > | isolation against ri.offset() (the line's standard offset alone), > | ... 71 lines of the commit log omitted. > > Produces 6 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ... > | FAIL: libstdc++-prettyprinters/debug.cc -flto print redirected > | FAIL: libstdc++-prettyprinters/debug.cc print redirected > | FAIL: libstdc++-prettyprinters/simple.cc -flto print redirected > | FAIL: libstdc++-prettyprinters/simple.cc print redirected > | ... and 2 more > > 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 > > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1968. (Require Linaro login) > Please let us know if you have a fix. > The attribution does not seem correct, as the above patch modifies tzdb.cc source file and does not touch the container. > > 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_gcc_check--master-aarch64-build/builds/… > 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-build/builds/… > The list of [ignored] baseline and flaky failures are in > * > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > > Current build : > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > Reference build : > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > > 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 >

3 weeks, 5 days

Re: [Linaro-TCWG-CI] 2025-09-21-gb3752b8ab8: Failure on aarch64

by Maxim Solodovnik

Hello, would you be so kind to point me to the logs of what was failed? :)) (I was unable to find any meaningful info regarding what is wrong :(( ) BTW maybe it would be better to start discussion at https://github.com/fujitsu/compiler-test-suite/pull/61 ? :) On Sat, 11 Jul 2026 at 21:48, <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 tcwg_flang_test/main-aarch64-O0-debug, after: > | commit 2025-09-21-gb3752b8ab8 > | Author: Maxim Solodovnik <solomax666(a)gmail.com> > | Date: Thu Jul 9 02:58:11 2026 +0000 > | > | OpenMP specific tests are excluded if OpenMP is absent (#61) > | > | * OpenMP specific tests are excluded if OpenMP is absent > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # build_llvm -- clang;lld;flang;clang-tools-extra openmp : > | 0 > | # test_llvm: > | # FAILED > | # First few build errors in logs: > | > | From > | # reset_artifacts: > | -10 > | # build_llvm -- clang;lld;flang;clang-tools-extra openmp : > | 0 > | # test_llvm: > | 1 > > Used configuration : > tcwg_flang_test/main-aarch64-O0-debug > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-2245. (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… > > 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/fujit… > > Full commit : https://github.com/fujitsu/compiler-test-suite/commit/b3752b8ab8bb7b0ec0bd7… -- Best regards, Maxim

4 weeks

Fwd: [Linaro-TCWG-CI] gcc patch #138844: Failure on arm

by jeevitha

Hi All, The changes in this patch are limited to the rs6000 backend and only introduce a new machine mode (`TDOmode`) with corresponding rs6000-specific handling. Since the changes are target-specific, I'm not sure why they would cause a bootstrap failure on the ARM configuration. Could this be an unrelated or flaky CI failure? For context, the other CI results for this patch are: https://patchwork.sourceware.org/project/gcc/patch/993e1e61-3bb4-4d74-b507-… * `linaro-tcwg-bot/tcwg_simplebootstrap_build--master-arm-bootstrap`: **Failed** * `linaro-tcwg-bot/tcwg_gcc_build--master-aarch64`: **Passed** * `linaro-tcwg-bot/tcwg_gcc_build--master-arm`: **Passed** * `linaro-tcwg-bot/tcwg_simplebootstrap_build--master-aarch64-bootstrap`: **Passed** Thanks, Jeevitha -------- Forwarded Message -------- X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <ci_notify(a)linaro.org> Received: from ltc-imap-p9a.rchland.ibm.com ([unix socket]) by ltc-imap-p9a.rchland.ibm.com (Cyrus 3.0.7-28.el8_10 Fedora) with LMTPA; Thu, 09 Jul 2026 19:55:24 -0500 X-Cyrus-Session-Id: ltc-imap-p9a.rchland.ibm.com-861175-1783644924-2-1779235549232312115 X-Sieve: CMU Sieve 3.0 Received: from localhost (localhost.localdomain [127.0.0.1]) by ltc-imap-p9a.rchland.ibm.com (Postfix) with ESMTP id E2079818AF44C for <jeevitha(a)imap.linux.ibm.com>; Thu, 9 Jul 2026 19:55:24 -0500 (CDT) X-Virus-Scanned: amavis at linux.ibm.com X-Spam-Flag: NO X-Spam-Score: 0.204 X-Spam-Level: X-Spam-Status: No, score=0.204 tagged_above=-9999 required=6.2 tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NORMAL_HTTP_TO_IP=0.001, NUMERIC_HTTP_ADDR=0.001, SPF_HELO_NONE=0.001, WEIRD_PORT=0.001] autolearn=disabled Received: from ltc-imap-p9a.rchland.ibm.com ([127.0.0.1]) by localhost (ltc-imap-p9a.rchland.ibm.com [127.0.0.1]) (amavis, port 10024) with LMTP id Ik3PP5N3ZHK9 for <jeevitha(a)imap.linux.ibm.com>; Thu, 9 Jul 2026 19:55:10 -0500 (CDT) Received: from mx1.linux.ibm.com (ltc-mx1-p9a.rchland.ibm.com [9.5.196.147]) by imap.linux.ibm.com (Postfix) with ESMTPS id 40DB6818AF295 for <jeevitha(a)imap.linux.ibm.com>; Thu, 9 Jul 2026 19:55:10 -0500 (CDT) Received: from smtprelay02.wdc07v.mail.ibm.com (unknown [9.208.129.120]) by mx1.linux.ibm.com (Postfix) with ESMTPS id EA666205250 for <jeevitha(a)linux.ibm.com>; Thu, 9 Jul 2026 19:55:09 -0500 (CDT) Received: from smtpav05.wdc07v.mail.ibm.com (smtpav05.wdc07v.mail.ibm.com [10.39.53.232]) by smtprelay02.wdc07v.mail.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 66A0t9pY51249502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:09 GMT Received: from smtpav05.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 1800758059 for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:09 +0000 (GMT) Received: from smtpav05.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id F068558061 for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:08 +0000 (GMT) Received: from ppma11.dal12v.mail.ibm.com (unknown [10.241.166.155]) by smtpav05.wdc07v.mail.ibm.com (Postfix) with ESMTPS for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:08 +0000 (GMT) Received: from pps.filterd (ppma11.dal12v.mail.ibm.com [127.0.0.1]) by ppma11.dal12v.mail.ibm.com (8.18.1.7/8.18.1.7) with ESMTP id 66A0nj9v017242 for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:08 GMT Authentication-Results: dal12v.mail.ibm.com; spf=softfail smtp.mailfrom=ci_notify(a)linaro.org; dkim=pass header.d=linaro.org header.s=google; dmarc=pass header.from=linaro.org Received: from mx0b-001b2d05.pphosted.com (mx0b-001b2d05.pphosted.com [205.220.172.48]) by ppma11.dal12v.mail.ibm.com (PPS) with ESMTPS id 4f7f6yfc38-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:06 +0000 (GMT) Received: from pps.filterd (m0373562.ppops.net [127.0.0.1]) by mx0b-001b2d05.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 669M6q3h2930946 for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:05 GMT Authentication-Results: ppops.net; spf=pass smtp.mailfrom=ci_notify(a)linaro.org; dkim=pass header.s=google header.d=linaro.org Received: from mail-qk1-f174.google.com (mail-qk1-f174.google.com [209.85.222.174]) by mx0b-001b2d05.pphosted.com (PPS) with ESMTPS id 4fam5eav0e-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:05 +0000 (GMT) Received: by mail-qk1-f174.google.com with SMTP id af79cd13be357-92e67555e24so16515985a.3 for <jeevitha(a)linux.ibm.com>; Thu, 09 Jul 2026 17:55:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1783644905; x=1784249705; darn=linux.ibm.com; h=list-id:content-type:mime-version:subject:message-id:to:reply-to :date:from:from:to:cc:subject:date:message-id:reply-to:content-type; bh=4+boJic9Z+2+iemk9uIpfZbFIsdxvdLiBrC89rSo71A=; b=fm0v1+3FPg0HqLoZyB1TBow87sPbwSXVQ+KlYQN1IgLdI8A3reZZFGJ8NStZUNrxxY DikCITundRkgUjfULlIELsIZFNNgUgXn0hhNhyRntODZS1DolV1+hTTWs2Jjz2VRp+hq 1UpvAjsUMeR6d9pJM46bbqwNnv0s4fGyNYeMiIAS3SGNMCWRnnIps5zo26A05vrK7SOv Nd5XU4Py061x62ZuI+LBS3GHRsbWadYghq0VAzS2fGn3w+pRJZDvADqyP8aqOQIfTufN s3fqtFEhQOfnv0RWCk17m8EwhU7VmD1LsvILdGl3eDdDj6cQL6+GthGLDkmz9ISTAa61 TYzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1783644905; x=1784249705; h=list-id:content-type:mime-version:subject:message-id:to:reply-to :date:from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to:content-type; bh=4+boJic9Z+2+iemk9uIpfZbFIsdxvdLiBrC89rSo71A=; b=ZRbhEw1+CFPvTQulfmlpKhaEGrAEwvI1dQm3rVPyA4aaMA5FlfraZDJVVfng/P0CiO Pi/nOhPq1fkmtK+NYmDyeLiG7zkaeLdtjUVEH7OkHh/9gQC9pKnQd8qLgGNOA9Q7EAak vFz14sqPmWpo6hHhRQ2khl8JeCy02Vp0upo5LHED5aQnfh99No7CEvNDf/z/zDTQGtW7 9nNzjH0lVo07rpt3fjTS/9/4/snFBJQPmratje/qTIRMVvM97JXtJlBrgwzXJ6AvgYak kisYU+UguA3FIP4hI1H202uAgW2M8rfZVMkSsjs1porgVZS6YeCMUoeRBTO4Oka4fXme pUew== X-Gm-Message-State: AOJu0Yxda79eYHKZMmZ6/dc2/B9wN0aGK5g83yeAfE9cafHhnN3eTLPm hp0mF/YHISgXEPLK6J65FU28bShyGb8De6hV3ITGsXrZI0OCJL2zo6scQw03jYvS21HnGzWOi1v 4ohCs X-Gm-Gg: AfdE7cnGBZ0g2LvpXgPDLAnsYUoDpcn9CqPUjRaAs/AHxBEqE2K1RD3tkJNEKSuanh/ 5TXnZeuA2YI08/ohzv55OyXRB3pzOm1NaQpURn6SV/OjwIH/q0bkurgUabU4S1Yj32WOgXGPYPa ZL6hy8y3TtpWUtoxLTkXgC/hW4oLONKKEChttfHxKvFsRvK5w7UjP5lQUqVmDai17KT8XnKqzzO RGW8PKdJV6v0e2JhVMKwRD8UdXoIoBqqt8fOtI0kB3l+Ry3CsbM4HwiVLvIkbywCf9D3NiKinrz vM5h+XNFSkPy/qNS2pneF+wQNY4w3Hf28euuddjAwhzgyMC9MuLzd5OR14qFodboN5xjHFm9WEr iSJEbKwY35FXwGT7K2U6Jk97Dddje+96KZniG8GRxDkiirCafRDbhcx6536bVPBVJWFtuQUN4QD iJ3tBjSi8sm8Gddv//OEpqHQwcoheWdGuJOsGQTNF8O7XZA7pzHkQndq5yzskUxkLsingO/JAP/ v9WdLo= X-Received: by 2002:a05:620a:19a0:b0:92e:7068:1de6 with SMTP id af79cd13be357-92ecf68ccf9mr964082685a.56.1783644904639; Thu, 09 Jul 2026 17:55:04 -0700 (PDT) Received: from 72d3563a6d18 (ec2-54-172-246-49.compute-1.amazonaws.com. [54.172.246.49]) by smtp.gmail.com with ESMTPSA id af79cd13be357-92ee5d36a22sm73492585a.39.2026.07.09.17.55.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Jul 2026 17:55:03 -0700 (PDT) From: ci_notify(a)linaro.org X-Google-Original-From: tcwg-validation(a)linaro.org Date: Fri, 10 Jul 2026 00:55:03 +0000 (UTC) Reply-To: linaro-toolchain(a)lists.linaro.org To: jeevitha(a)linux.ibm.com Message-ID: <1196044404.73385.1783644903827@72d3563a6d18> Subject: [Linaro-TCWG-CI] gcc patch #138844: Failure on arm MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_73384_1250231304.1783644903313" X-Jenkins-Job: TCWG Precommit tcwg_simplebootstrap_build/master-arm-bootstrap X-Jenkins-Result: FAILURE List-ID: X-CLX-Shades: MLX X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwNzEwMDAwNSBTYWx0ZWRfX/QbUtdwXAKAB aWo86CEW34/md+P55nH35zFMSa2utkEnxxLt7o+dkvDccyzbsv+kCv+R5Ob/zpzeT3IFG6tTKEX KojMivWE5yZZRKZfnHy6KrVMJq7uxknnjOHmUxaPpoghRzH7iI8mGL7Es3zP2+trgatuPYUHNou Wfr6aTqeRdiwXGOgSqfkfVTeIM3x8X3r/yTaeXdBntLNtfAif1eu7STxhaRQ1aUC+c4ADFdOJk+ Zg15RbXwWCRN1VADNWCBH6pkBvyKctVZCw6KKBe7MxvpoYQBMbM0Yyo+kbMlzlK0NeN/qRg29qJ D79wXolwL7pSMan4PHXLrFTXiCHYRNhnAFcjisYEpsQScaRTsOs6OhmL7bnMxjureLr79IFAxUo zhwawIYeaPpZ93Wv1Wvcd5ji1R9C92ugpf6KeJ4OujFErbyZoUIOtoMOwwAXwUy5Z9tNtKWCwpZ mvvemM4gvmBe34G4ecI2EiYNyUyW3Hp8Odf/VQq0goxgQ+BZPL596CjWOhNAJ X-Proofpoint-GUID: XA-23DF6gEgcniOZwVkQ-DTZRVYB2VTm X-CLX-Response: 1TFkXGxwfEQpMehcbEhkRCllEF28FHUcfGHloaWxOEQpYWBdvQW5PH316Z2x 6exEKeE4XaFxna3haWE4ae28RCnhLF29Bbk8ffXpnbHp7EQp5TBdiBVkBf21mbWFfQBEKQ0gXBx kSGhEKQ1kXBxsdGhEKQ0kXGgQaGhoRCllNF2dmchEKWUkXGnEaEBp3BhseH3EYHRAadwYYGgYaE QpZXhdsbHkRCklGF0NIR3UZdUJFWV5PThEKSUcXeE9NEQpDThdyawcYGW5sHE1vTUlEQ2VwXXxB ewdufnB4fHNoGHx+RxEKWFwXHwQaBB4YGgUbGgQbGhoEGxkeBBkeEBseGh8aEQpeWRdCQk9PbxE KTVwXHB4TEQpMWhd4aV1NaxEKRVkXbGtrEQpMXxd6BQUFBQUFBQUFHREKTEYXb2trY2trEQpCTx dlaVBnYUZ9bBsFBREKQ1oXGBoTBBIfBBgYGAQbHR4RCkJeFxsRCkJcFxsRCl5OFxsRCkJLF3pMT V57aEhdaRoFEQpCSRd6TE1ee2hIXWkaBREKQkUXbEVsHmMdTBJCXEIRCkJOF3pMTV57aEhdaRoF EQpCTBdsRWweYx1MEkJcQhEKQmwXbEVsHmMdTBJCXEIRCkJAF2Viex1zH39ubW5FEQpCWBdnS0l aQHlTeE5NfhEKWlgXGREKeUMXY1tkYn1laUlhE2MRCllLFx8THh0RClpLFx8THh0RCnBnF29CG3 kebn5JQhlCEBkaEQpwaBdrR1lZaFgBG3B7UxAZGhEKcGgXa1tOa0VnXVNoSXoQGRoRCnBoF2sbR HJbT3JAW2hoEBkaEQpwaBdtHUJJGV5JXm96SxAZGhEKcGgXYVxiGnJAbUxGa1gQGRoRCnBoF2Uc bHBHHm56a0NeEBkaEQpwaBdnY1pEUmJLX1p/YhAZGhEKcGgXaUQdQ1tle2BZfUIQGRoRCnB9F2Q SaEBOR2wbRFBiEBkaEQpwZxdgfmBEQF1iXX1eeBAeEhEKcGcXZm5GZnphXEVJQEsQGRoRCnB9F2 5kXGBiQH5aHEAbEBkaEQpwfRdlR21kSWxsGW9DGhAZGhEKcH0XbVlzbEFwfH0SGgEQGRoRCnB9F 3pcGkBQTRpGaWdNEBkaEQpwfxdpfWkfT2QTGEBobhAbHhsRCnBfF21tQXxSQWFNWE0ZEBkaEQpw fxdgY15iYX9iUkRmQxAZGhEKcF8XZXIcHH5/WU9rQR0QGRoRCnBDF25iGFhuc2trWUtPEBkaEQp tfhcaEQpYTRdLESA= X-Authority-Analysis: v=2.4 cv=A6Rc+aWG c=1 sm=1 tr=0 ts=6a5042e9 cx=c_pps a=UZBReMFAb/XnTJ6n9KjCdA==:117 a=4i7SwhsebvtlREVtV86eDg==:17 a=RAioF0-LDSMA:10 a=y97k-4bRjHMA:10 a=Kan8h273Bse8B8Jy5C1n:22 a=Tf50yhtgai_kYZK-W9C0:22 a=h-DKXlNGRfCIpgHfyL0k:22 a=CCpqsmhAAAAA:8 a=F3QvygtyAAAA:8 a=VnNF1IyMAAAA:8 a=KKAkSRfTAAAA:8 a=VCkTNp8_fUlclFnFz1EA:9 a=lqcHg5cX4UMA:10 a=QEXdDO2ut3YA:10 a=cT35ftHboTvi5MAKYRRR:22 a=ul9cdbp4aOFLsgKbc677:22 a=Zmt_HxeAg-O1BNttnniw:22 a=cvBusfyB2V15izCimMoJ:22 X-Proofpoint-Spam-Info: AW1haW4tMjYwNzEwMDAwNSBTYWx0ZWRfX7QmG5Onrzk8Q 33gso025apajvQ721u6LbWkssi7jJCuoq+Pv2gu1BajkqrfRl6RkIE7VScbICpQS4CkZmxeq7+o L84NC/U0AJTw57i3sg16bzAvuZf5yCs= X-Proofpoint-ORIG-GUID: XA-23DF6gEgcniOZwVkQ-DTZRVYB2VTm X-Proofpoint-Banner-Trigger: inbound X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1143,Hydra:6.1.134,FMLib:17.12.100.49 definitions=2026-07-09_04,2026-07-09_04,2025-10-01_01 X-Proofpoint-Spam-Details: rule=inbound_notspam policy=inbound score=1 impostorscore=0 lowpriorityscore=0 suspectscore=0 clxscore=165 adultscore=0 malwarescore=0 spamscore=0 phishscore=0 priorityscore=183 bulkscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=inbound adjust=1 reason=mlx scancount=1 engine=8.22.0-2606150000 definitions=main-2607100005 domainage_hfrom=5947 domainage_replyto=5947 X-TM-AS-GCONF: 00 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In simplebootstrap_build master-arm-bootstrap, after: | gcc patch https://patchwork.sourceware.org/patch/138844 | Author: jeevitha <jeevitha(a)linux.ibm.com> | Date: Fri Jul 10 00:08:25 2026 +0530 | | [PATCH] rs6000: Add TDOmode support | | Hi All, | | The following patch has been bootstrapped and regtested on powerpc64le-linux. | ... 15 lines of the commit log omitted. | ... applied on top of baseline commit: | d06b04d90ca Remove uses of `CONSTEXPR` macro Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe bootstrap: | # FAILED | # First few build errors in logs: | # 01:33:42 make[2]: *** [Makefile:26651: compare] Error 1 | # 01:33:42 make[1]: *** [Makefile:26631: stage3-bubble] Error 2 | # 01:33:42 make: *** [Makefile:1140: all] Error 2 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe bootstrap: | 1 Used configuration : *CI config* tcwg_simplebootstrap_build master-arm-bootstrap *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf 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-arm-boots… 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-arm-boots… Current build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-arm-boots… Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-arm-boots… Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.

4 weeks

Installing LibXML2 on the lldb-aarch64-windows build bot

by Charles Zablit

Hi, I work on lldb on Windows at Apple. We have done some work recently to bring lldb-server.exe up to par with the current lldb implementation on Windows, which uses an in-process debugger. This new implementation matches other platforms like macOS and Linux which also use a debug server. We have full test parity (all the tests that work with the in process debugger also work with lldb-server.exe). We are actively testing both configs in CI: https://ci-external.swift.org/job/lldb-windows/job/main/ We are ready to make the change to make lldb-server.exe the default implementation on Windows. In the codebase, this means switching the flag here: https://github.com/llvm/llvm-project/blob/d981ae2be3be6fd65ad66e763fcc20b3a…. However, building lldb-server.exe requires libxml2, which the buildbot https://lab.llvm.org/buildbot/#/builders/141 does not have. I’m reaching out to you to ask if it’s please possible to install libxml2 on the bot? The easiest way to do that would be to run “vcpkg install libxml2” on the bot. Vcpkg is already in the PATH, so CMake should pick up the libxml2 includes automatically once it’s installed. I am happy to validate the build once the installation is complete and will address any issues that may arise. Best regards, Charles Zablit

1 month

Re: [Linaro-TCWG-CI] gcc patch #138785: Failure on arm

by H.J. Lu

On Thu, Jul 9, 2026 at 11:59 AM <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-arm-bootstrap, after: > | gcc patch https://patchwork.sourceware.org/patch/138785 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Wed May 13 08:27:50 2026 +0800 > | > | [PATCH v2] x86: Honor preserve_none ABI for x86-64 MS calls > | > | In 64-bit mode, preserve_none attribute uses a different calling > | convention. Ignore MS ABI with preserve_none attribute to always > | use the preserve_none calling convention with preserve_none > | ... 45 lines of the commit log omitted. > | ... applied on top of baseline commit: > | e5af677005c Daily bump. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap: > | # FAILED > | # First few build errors in logs: > | # 00:07:41 make[3]: [Makefile:1882: armv8l-unknown-linux-gnueabihf/bits/largefile-config.h] Error 1 (ignored) > | # 00:58:25 make[3]: [Makefile:1882: armv8l-unknown-linux-gnueabihf/bits/largefile-config.h] Error 1 (ignored) > | # 01:14:22 collect2: error: ld returned 1 exit status > | # 01:14:22 make[3]: *** [/home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/lto/Make-lang.in:93: lto1] Error 1 > | # 01:14:22 collect2: error: ld returned 1 exit status > | # 01:14:22 make[3]: *** [/home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/cp/Make-lang.in:147: cc1plus] Error 1 > | # 01:14:23 collect2: error: ld returned 1 exit status > | # 01:14:23 make[3]: *** [/home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/c/Make-lang.in:88: cc1] Error 1 > | # 01:14:23 collect2: error: ld returned 1 exit status > | # 01:14:23 make[3]: *** [/home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/objc/Make-lang.in:78: cc1obj] Error 1 > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap: > | 1 The only file which my patch changes is gcc/config/i386/i386.cc. How can it impact arm? > Used configuration : > *CI config* tcwg_simplebootstrap_build master-arm-bootstrap > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > 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-arm-boots… > 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-arm-boots… > > Current build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-arm-boots… > Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-arm-boots… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files. -- H.J.

1 month

[Linaro-TCWG-CI] glibc-2.43.9000-463-gfcea66cd468: 1 regression on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In glibc_check master-arm, after: | commit glibc-2.43.9000-463-gfcea66cd468 | Author: DJ Delorie <dj(a)redhat.com> | Date: Thu Jun 25 23:30:39 2026 -0400 | | Add system-wide tunables: Filters | | Add support for [proc:*] syntax where * matches /proc/self/exe | (fallback: argv[0] unless AT_SECURE). Tunables after such a | line are limited to matching processes. | ... 14 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-tunconf1 Used configuration : *CI config* tcwg_glibc_check master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1958. (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_glibc_check--master-arm-build/builds/10… 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-arm-build/builds/10… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… 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=fcea66cd4685f9f3719e…

1 month

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain