linaro-toolchain

linaro-toolchain@lists.linaro.org

3 participants
5459 discussions

Start a nNew thread

[Linaro-TCWG-CI] llvmorg-20-init-8106-ge36a39346796: Failure on aarch64

by ci_notify＠linaro.org

1 day, 15 hours

Re: [Linaro-TCWG-CI] v6.11-rc4-291-g16531118ba63: Failure on aarch64

by Nathan Chancellor

On Fri, Oct 04, 2024 at 07:05:02AM +0000, ci_notify(a)linaro.org wrote: ... > | commit v6.11-rc4-291-g16531118ba63 > | Author: Denis Benato <benato.denis96(a)gmail.com> > | Date: Sat Aug 24 16:11:22 2024 +0200 > | > | iio: bmi323: peripheral in lowest power state on suspend > | > | The bmi323 is mounted on some devices that are powered > | by an internal battery: help in reducing system overall power drain > | while the system is in s2idle or the imu driver is not loaded > | ... 5 lines of the commit log omitted. This should be fixed with https://git.kernel.org/jic23/iio/c/506a1ac4c4464a61e4336e135841067dbc040aaa which is on its way for an -rc release. Cheers, Nathan

2 days, 21 hours

Re: [Linaro-TCWG-CI] llvmorg-20-init-7781-g0f973ac783aa: FAIL: 1 regressions on aarch64

by Peter Klausler

The error message for that test is correct. From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Thursday, October 3, 2024 at 06:51 To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>, itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>, t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>, Peter Klausler <pklausler(a)nvidia.com> Subject: [Linaro-TCWG-CI] llvmorg-20-init-7781-g0f973ac783aa: FAIL: 1 regressions on aarch64 External email: Use caution opening links or attachments Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinaro.at…<https://linaro.atlassian.net/browse/LLVM-1374> , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_flang_test/main-aarch64-Ofast-sve_vla after: | commit llvmorg-20-init-7781-g0f973ac783aa | Author: Peter Klausler <pklausler(a)nvidia.com> | Date: Wed Oct 2 08:54:49 2024 -0700 | | [flang] Tag warnings with LanguageFeature or UsageWarning (#110304) | | (This is a big patch, but it's nearly an NFC. No test results have | changed and all Fortran tests in the LLVM test suites work as expected.) | | ... 24 lines of the commit log omitted. FAIL: 1 regressions The configuration of this build is: * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : cmake -GNinja -DCMAKE_C_COMPILER="$WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$WORKSPACE/test/test-suite" regressions.sum: | === test-suite tests === | | Running test-suite:Fujitsu/Fortran/0384 ... | NOEXE: test-suite :: Fujitsu/Fortran/0384/Fujitsu-Fortran-0384_0053.test | | # "NOEXE" means : the test program cannot be compiled You can find the failure logs in *.log.1.xz files in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…> The full lists of regressions and improvements as well as configure and make commands are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…> The list of [ignored] baseline and flaky failures are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…> -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…> Reference build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…> Fujitsu testsuite : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/fujitsu/compiler-test-suite/> Instruction to reproduce the build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit-us.li…<https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…> Full commit : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/llvm/llvm-project/commit/0f973ac783aa100cfbce1cd2c6e8a3a…>

3 days, 22 hours

[Linaro-TCWG-CI] binutils-2_41-release-4424-g7ecf0250f7f: FAIL: 1 regressions 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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1359 , please let us know if you are looking at the problem and/or when you have a fix. In binutils_check master-arm after: | commit binutils-2_41-release-4424-g7ecf0250f7f | Author: Nick Clifton <nickc(a)redhat.com> | Date: Mon Sep 30 14:41:11 2024 +0100 | | Improve the placement of orphan note sections. | | PR 32219 FAIL: 1 regressions regressions.sum: | === ld tests === | | Running ld:ld-elf/shared.exp ... | FAIL: Run with libfunc1.so comm1.o | | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/1679/artifa… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/1679/artifa… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/1679/artifa… The configuration of this build is: CI config tcwg_binutils_check master-arm -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/1679/artifa… Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/1678/artifa… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=7ecf0250f7f08…

6 days, 22 hours

Re: [Linaro-TCWG-CI] gcc-15-3575-gc07cf418fdde: FAIL: 2 regressions on master-thumb_m0_eabi

by Jonathan Wakely

On Mon, 30 Sept 2024 at 07:22, <ci_notify(a)linaro.org> wrote: > > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1358 , please let us know if you are looking at the problem and/or when you have a fix. > > In arm-eabi cortex-m0 soft after: > > | commit gcc-15-3575-gc07cf418fdde > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Tue Sep 10 14:25:41 2024 +0100 > | > | libstdc++: std::string move assignment should not use POCCA trait [PR116641] > | > | The changes to implement LWG 2579 (r10-327-gdb33efde17932f) made > | std::string::assign use the propagate_on_container_copy_assignment > | (POCCA) trait, for consistency with operator=(const basic_string&). > | ... 18 lines of the commit log omitted. > > FAIL: 2 regressions > > regressions.sum: > | === libstdc++ tests === > | > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 21_strings/basic_string/allocator/116641.cc -std=gnu++17 (test for excess errors) > | UNRESOLVED: 21_strings/basic_string/allocator/116641.cc -std=gnu++17 compilation failed to produce executable > | > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… === libstdc++ Summary === # of expected passes 6036 # of unexpected failures 4689 <<< !!! Is that normal for this configuration?! The new testcase fails for the same reason as the 4000 other tests: /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld: (__deregister_frame_info): Unknown destination type (ARM/Thumb) in /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/./gcc/crtbegin.o crtstuff.c:(.text+0x5e): dangerous relocation: unsupported relocation So I don't think this is a problem in the commit, I think it's just a configuration that isn't well supported. > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… > > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv6s-m -mtune=cortex-m0 -mfloat-abi=soft -mfpu=auto > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/c07cf418fdde0c192e370a8d76a991cc72…

6 days, 23 hours

Re: [Linaro-TCWG-CI] gcc patch #97864: FAIL: 3 regressions on arm

by Jason Merrill

On 9/23/24 2:08 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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In gcc_check master-arm after: > > | gcc patch https://patchwork.sourceware.org/patch/97864 > | Author: Jason Merrill <jason(a)redhat.com> > | Date: Mon Sep 23 11:06:11 2024 -0400 > | > | libstdc++: #ifdef out #pragma GCC system_header > | > | Tested x86_64-pc-linux-gnu, OK for trunk? > | > | -- 8< -- > | > | In r15-3714-gd3a7302ec5985a I added -Wsystem-headers to the libstdc++ build > | ... 379 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 4700ad1c78c c++: diagnose this specifier in requires expr [PR116798] > > FAIL: 3 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 17_intro/headers/c++2011/parallel_mode.cc (test for excess errors) > FAIL: 17_intro/headers/c++2014/parallel_mode.cc (test for excess errors) > FAIL: 17_intro/headers/c++2017/parallel_mode.cc -std=gnu++17 (test for excess errors) > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/9301/artifac… > 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-arm-precommit/9301/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/9301/artifac… Thanks, I believe https://gcc.gnu.org/pipermail/gcc-patches/2024-September/663711.html should fix this.

1 week

Re: [Linaro-TCWG-CI] 29 patches in glibc: FAIL: 1 regressions on arm

by Florian Weimer

* ci notify: > Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. > > In glibc_check master-arm after: > > | 29 patches in glibc > | Patchwork URL: https://patchwork.sourceware.org/patch/98131 > | 59fbaae3a6e Optimize various ways to obtain the page size using <bits/pagesize.h> > | 564bcbe0067 posix: Use <support/next_to_fault.h> in tst-fnmatch3 > | 27a360de01d malloc: Use volatile as compiler barrier in tst-memalign, tst-valloc > | e24dfc8d9a8 Linux: Optimize getpagesize using <sys/pagesize.h> > | 3283915ffd0 Install the <sys/pagesize.h> header file > | ... and 24 more patches in glibc > | ... applied on top of baseline commit: > | 6948ee4edf0 stdio-common: Fix memory leak in tst-freopen4* tests on UNSUPPORTED > > FAIL: 1 regressions > > regressions.sum: > | === glibc tests === > | > | Running glibc:elf ... > | XPASS: elf/tst-load-alignment Does this mean that the 32-bit arm tester uses a non-default toolchain that increases page alignment to 64 KiB? With my cross-tester, elf/tst-load-alignment fails as expected because the binaries can only be loaded on 4 KiB page systems, based on the program header layout. Thanks, Florian

1 week

Buildbot failure - clang-arm64-windows-msvc

by Julian Schmidt

Hello, a commit of mine seems to have broken your bot, but I am not sure how, because it is a timeout: https://lab.llvm.org/buildbot/#/builders/161/builds/2385. The commit is https://github.com/llvm/llvm-project/commit/e42cc3f42e6a36f4dfff40827819404… and touches Clang's unit tests. The build just before mine includes the previous commit of my own change, and it was green, which points at that commit being the culprit here. The commit brings in a custom command that generates ASTMatchersDocTests.cpp in the build directory for inclusion in the ASTMatchersTests unittest target/binary, but that target gets never built, and the file never generated, according to the logs. I therefore think that my changes to clang/unittests/ASTMatchers/ASTMatchersTest.h should be the most likely to have cause this. Do you have any experience with timeouts, or do you have/can acquire additional information about what has timed out? I have left the commit in-tree as clang-arm64-windows-msvc is the only bot I broke, and it is not clear why. On the other hand, clang-x64-windows-msvc and the other Windows bots are just fine, the same goes for other ARM but non-windows bots as well. Kind regards, Julian Schmidt

1 week

[Linaro-TCWG-CI] glibc-2.40.9000-213-gb300078d97a: FAIL: 4 regressions on aarch64

by ci_notify＠linaro.org

Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1357 , please let us know if you are looking at the problem and/or when you have a fix. In master-aarch64 after: | commit glibc-2.40.9000-213-gb300078d97a | Author: Florian Weimer <fweimer(a)redhat.com> | Date: Sat Sep 28 09:44:25 2024 +0200 | | Linux: Block signals around _Fork (bug 32215) | | This hides the inconsistent TCB state (missing robust mutex list) from | signal handlers. | | ... 1 lines of the commit log omitted. FAIL: 4 regressions regressions.sum: | === gdb tests === | | Running gdb:gdb.base/step-over-syscall.exp ... | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: find syscall insn in fork (timeout) | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: syscall number matches | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: find syscall insn in fork (timeout) | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: syscall number matches | | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one 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… The configuration of this build is: CI config tcwg_gnu_native_check_gdb master-aarch64 -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: 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://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=b300078d97a6892cb2fa…

1 week

Re: [Linaro-TCWG-CI] gcc-15-3899-g819098dc71f2: FAIL: 1 regressions: 1 improvements on aarch64

by Sam James

ci_notify(a)linaro.org writes: > Dear contributor, our automatic CI has detected problems related to > your patch(es). Please find some details below. If you have any > questions, please follow up on linaro-toolchain(a)lists.linaro.org > mailing list, Libera's #linaro-tcwg channel, or ping your favourite > Linaro toolchain developer on the usual project channel. > > We understand that it might be difficult to find the necessary logs or > reproduce the issue locally. If you can't get what you need from our > CI within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1356 , please let us know if you are looking at the problem and/or when you have a fix. > > In gcc_check master-aarch64 after: > > | commit gcc-15-3899-g819098dc71f2 > | Author: Sam James <sam(a)gentoo.org> > | Date: Thu Sep 26 15:43:33 2024 +0100 > | > | testsuite: XFAIL gfortran.dg/initialization_25.f90 properly > | > | The test was disabled/XFAIL'd informally in r0-100012-gcdc6637d7c78ec, > | but r15-3890-g34bf6aa41ba539 didn't realize this, causing a FAIL. > | > | ... 7 lines of the commit log omitted. > > FAIL: 1 regressions: 1 improvements > Thanks, this is PR116858 and I'll handle it today or tomorrow at the latest. > regressions.sum: > | === gfortran tests === > | > | Running gfortran:gfortran.dg/dg.exp ... > | FAIL: gfortran.dg/initialization_25.f90 -O xfail *-*-* (test for errors, line 11) > | > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > > improvements.sum: > | === gfortran tests === > | > | Running gfortran:gfortran.dg/dg.exp ... > | FAIL: gfortran.dg/initialization_25.f90 -O (test for errors, line 11) > | > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2668/artifac… > 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-build/2668/artifac… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2668/artifac… > > The configuration of this build is: > CI config tcwg_gcc_check master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2668/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2667/artifac… > > Instruction to reproduce the build : > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/819098dc71f2079aedc15a904ab5f17f07…

1 week, 3 days

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain