linaro-toolchain

linaro-toolchain@lists.linaro.org

14 participants
5371 discussions

Re: [Linaro-TCWG-CI] gcc patch #88475: Failure on aarch64

by Christophe Lyon

On Mon, 15 Apr 2024 at 12:15, <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 appreciate 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_build master-aarch64 after: > > | gcc patch https://patchwork.sourceware.org/patch/88475 > | Author: Fei Gao <gaofei(a)eswincomputing.com> > | Date: Mon Apr 15 06:33:17 2024 +0000 > | > | optimize Zicond conditional select cases. > | > | When one of the two input operands is 0, ADD and IOR are functionally > | equivalent. > | ADD is slightly preferred over IOR because ADD has a higher likelihood > | of being implemented as a compressed instruction when compared to IOR. > | C.ADD uses the CR format with any of the 32 RVI registers availble, > | ... 21 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 7f4ba5480e0 testsuite: i386: Restrict gcc.target/i386/fhardened-1.c etc. to Linux/GNU > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > # FAILED > # First few build errors in logs: > # 00:11:10 make[2]: *** [/home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/fortran/Make-lang.in:142: fortran.install-html] Error 1 > # 00:11:10 make[1]: *** [Makefile:5002: install-html-gcc] Error 1 > # 00:11:10 make: *** [Makefile:1895: do-install-html] Error 2 > Please ignore this false alarm: it was caused by a change in our build scripts. The problem should now be fixed. I've manually retriggered the validation, the status should be updated soon in patchwork. Thanks, Christophe > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > 1 > > The configuration of this build is: > CI config tcwg_gcc_build 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_build--master-aarch64-precommit/8188/art… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/1921/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.

2 days, 20 hours

RE: [Linaro-TCWG-CI] 4 patches in gdb: FAIL: 1 regressions: 1 progressions on arm

by Metzger, Markus T

Hello, > | 4 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/88278 > | 343a2568d2c gdb, infrun: fix multi-threaded reverse stepping > | a4cfc3d32a8 gdb, infrun, record: move no-history notification into >normal_stop > | fc70b453e32 gdb, infrun, record: fix hang when step-over fails with no- >history > | 45548f364fd gdb, infrun, btrace: fix reverse/replay stepping at end of >execution history > | ... applied on top of baseline commit: > | 31c21e2c13d [gdb/testsuite] Fix gdb.threads/access-mem-running-thread- >exit.exp with clang > >FAIL: 1 regressions: 1 progressions > >regressions.sum: > === gdb tests === > >Running gdb:gdb.threads/interrupt-while-step-over.exp ... >FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: >iter=6: wait for stops (timeout) The log contains several FAILs at different iterations, yet this report lists a single new fail at iteration 6 IIUC. Is this test known to be flaky? I tried reproducing this on x86-64 but couldn't find any flakiness with this test. >progressions.sum: > === gdb tests === > >Running gdb:gdb.threads/detach-step-over.exp ... >FAIL: gdb.threads/detach-step-over.exp: breakpoint-condition- >evaluation=host: target-non-stop=on: non-stop=on: displaced=off: >test_detach_command: iter 2: attach (GDB internal error) What is a 'progression'? The log again contains several fails in this test. I also found the same GDB internal error in xfails.xfail on iter 3 instead of 2. I tried reproducing this on x86-64 but couldn't find any flakiness with this test. >You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm- >precommit/2150/artifact/artifacts/artifacts.precommit/00-sumfiles/ >The full lists of regressions and progressions as well as configure and make >commands are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm- >precommit/2150/artifact/artifacts/artifacts.precommit/notify/ >The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm- >precommit/2150/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail > >The configuration of this build is: >CI config tcwg_gdb_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_gdb_check--master-arm- >precommit/2150/artifact/artifacts >Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm- >build/1039/artifact/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. If those are indeed real fails introduced by my patches, any chance I can debug this on an x86-64 system? Via simulation, perhaps? thanks, Markus. Intel Deutschland GmbH Registered Address: Am Campeon 10, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de> Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928

3 days, 6 hours

[ACTIVITY] report week ending Apr 12

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - looking at some late-breaking patches for various more-or-less 9.0-worthy bugs - tagged rc3; looks like we'll need an rc4, though - back to looking at cleanups and refactorings of our reset handling: + add support for a new reset type RESET_TYPE_SNAPSHOT_LOAD so we can use a new-style reset method for the kind of "load new RNG seed into memory" task we can currently only do with qemu_register_reset_nosnapshotload() or with a Machine reset method + pass the reset type into all reset phase methods, not just 'enter' + experimenting with making Machine a subclass of Device, which should let us clean up some inconsistencies (like Machine having its own reset handling that's different from everything else) -- PMM

6 days, 6 hours

Re: [Linaro-TCWG-CI] gcc-14-9891-g5aa3fec38cc: FAIL: 12 regressions on aarch64

by Andre Simoes Dias Vieira

Yeah I'll fix this, looks like a testism due to changes in codegen between dev and commit versions, code improved too so it's the good type of testism ;) ________________________________________ From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Thursday, April 11, 2024 3:43 PM To: Andre Simoes Dias Vieira Cc: gcc-regression(a)gcc.gnu.org Subject: [Linaro-TCWG-CI] gcc-14-9891-g5aa3fec38cc: FAIL: 12 regressions on aarch64 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 appreciate 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-1192 , 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-14-9891-g5aa3fec38cc | Author: Andre Vieira <andre.simoesdiasvieira(a)arm.com> | Date: Wed Apr 10 16:29:46 2024 +0100 | | aarch64: Add support for _BitInt | | This patch adds support for C23's _BitInt for the AArch64 port when compiling | for little endianness. Big Endianness requires further target-agnostic | support and we therefor disable it for now. | | gcc/ChangeLog: | ... 24 lines of the commit log omitted. FAIL: 12 regressions regressions.sum: === gcc tests === Running gcc:gcc.target/aarch64/aarch64.exp ... FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g1 FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g16 FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g16p FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g1p FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g8 FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g8p FAIL: gcc.target/aarch64/bitfield-bitint-abi-align8.c check-function-bodies g1 ... and 6 more entries You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1842/artifac… The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1842/artifac… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1842/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/1842/artifac… Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1841/artifac… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… Full commit : https://github.com/gcc-mirror/gcc/commit/5aa3fec38cc6f52285168b161bab1a869d… List of configurations that regressed due to this commit : * tcwg_gcc_check ** master-aarch64 *** FAIL: 12 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1842/artifac… 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.

1 week

Re: [Linaro-TCWG-CI] v6.9-rc2-36-gfc4216add64ee: Failure on arm

by Thiago Jung Bauermann

ci_notify(a)linaro.org writes: > In CI config tcwg_kernel/gnu-master-arm-next-allyesconfig after: > > | commit v6.9-rc2-36-gfc4216add64ee > | Author: Samuel Holland <samuel.holland(a)sifive.com> > | Date: Fri Mar 29 00:18:28 2024 -0700 > | > | drm/amd/display: use ARCH_HAS_KERNEL_FPU_SUPPORT > | > | Now that all previously-supported architectures select > | ARCH_HAS_KERNEL_FPU_SUPPORT, this code can depend on that symbol instead > | of the existing list of architectures. It can also take advantage of the > | common kernel-mode FPU API and method of adjusting CFLAGS. > | > | ... 21 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_abe stage1: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 22511 > > From > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_abe stage1: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 22321 > # linux build successful: > all This problem still reproduces on next-20240410, so I reported it to the patch author. He responded here: https://lore.kernel.org/linux-arm-kernel/75a37a4b-f516-40a3-b6b5-4aa1636f9b… mentioning that it's a shortcoming of GCC on arm: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91970 Though Andrew Pinski has just disagreed with that assessment. -- Thiago

1 week

Pre-commit execution test for pr113363.f90

by Paul Richard Thomas

Hi there, Thanks for the heads-up on gcc patch #88281: 6 regressions on arm. I see from the log that the test timed-out and the core was dumped. I cannot reproduce this and can see nothing in the tree-dump that might cause a time out. I would appreciate some help on where the fault lies and what the cause might be. Best regards Paul Thomas

1 week

[ACTIVITY] Report for week #14

by Philippe Mathieu-Daudé

[QEMU maintenance] * Got involved offline via qemu-security@ for 2 bugs for 9.0, sent 2 patches: - virtio dma re-entrancy (use after free) https://lore.kernel.org/qemu-devel/20240404191339.5688-1-philmd@linaro.org/ - hw sdhci (overflow) https://lore.kernel.org/qemu-devel/20240404085549.16987-1-philmd@linaro.org/ * "Misc HW fixes for 9.0" pull request [Single binary] * Still working on sanitizing include/exec/, user emulation part * Analyzed how to merge libtcg system/user code, removing the compile-time uses of CONFIG_SOFTMMU. Left as a peer programming exercise with rth at MAD24 :)

1 week, 6 days

[ACTIVITY] report week ending 5 Apr

by Peter Maydell

Progress (short week, 3 days): * UM-2 [QEMU upstream maintainership] - more pullreq wrangling - more FEAT_NMI patchset review: I think I'm now finally done with this - looked at issue #2150 and produced a short standalone repro case from the logfile the user provided (which was from a boot of Windows) -- PMM

1 week, 6 days

Re: [Linaro-TCWG-CI] gcc patch #88035: FAIL: 1 regressions on aarch64

by Jonathan Wakely

On Thu, 4 Apr 2024 at 22:21, <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. Hi, The new testcase only works for targets where char is signed, because I forgot to add the assertions for the unsigned case. My own aarch64 testing found the same problem. I'll send a v2 patch shortly. Thanks for the useful CI service! > > We appreciate 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-aarch64 after: > > | gcc patch https://patchwork.sourceware.org/patch/88035 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Thu Apr 4 16:29:09 2024 +0100 > | > | libstdc++: Fix infinite loop in std::istream::ignore(n, delim) [PR93672] > | > | I would appreciate more eyes on this to confirm my conclusions about > | negative int_type values, and the proposed fix, make sense. > | > | Tested x86_64-linux. > | > | ... 32 lines of the commit log omitted. > | ... applied on top of baseline commit: > | dc8a25189dd Add gcov MC/DC tests for GDC > > FAIL: 1 regressions > > regressions.sum: > === libstdc++ tests === > > Running libstdc++:libstdc++-dg/conformance.exp ... > FAIL: 27_io/basic_istream/ignore/char/93672.cc -std=gnu++17 execution test > > > # of stable fails 61 > # of flaky entries 9 > # of all tests 890731 > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/5627/art… > The full lists of regressions and progressions as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/5627/art… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/5627/art… > > 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-precommit/5627/art… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1805/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.

1 week, 6 days

[Linaro-TCWG-CI] binutils-2_41-release-2766-ga9505c74206: FAIL: 1 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 appreciate 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-1188 , please let us know if you are looking at the problem and/or when you have a fix. In master-aarch64 after: | commit binutils-2_41-release-2766-ga9505c74206 | Author: H.J. Lu <hjl.tools(a)gmail.com> | Date: Mon Mar 11 09:51:06 2024 -0700 | | elf: Add _bfd_elf_link_m[un]map_section_contents | | To copy input section contents, add _bfd_elf_link_mmap_section_contents | and _bfd_elf_link_munmap_section_contents to mmap in the input sections. | | * elf-bfd.h (_bfd_elf_link_mmap_section_contents): New. | (_bfd_elf_link_munmap_section_contents): Likewise. | ... 13 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:wcsmbs ... FAIL: wcsmbs/tst-wcstod-round # of stable fails 1 # of flaky entries 16 # of all tests 4848 You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-aarch64-build… The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-aarch64-build… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-aarch64-build… The configuration of this build is: CI config tcwg_gnu_native_check_glibc 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_glibc--master-aarch64-build… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-aarch64-build… Reproduce last good and first bad builds: 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=a9505c74206cf… List of configurations that regressed due to this commit : * tcwg_gnu_native_check_glibc ** master-aarch64 *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… *** https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-aarch64-build…

1 week, 6 days

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain