Re: [Linaro-TCWG-CI] gcc-15-3575-gc07cf418fdde: FAIL: 2 regressions on master-thumb_m0_eabi
On Mon, 30 Sept 2024 at 07:22, 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@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 > | 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-build/547/artifact/artifacts/00-sumfiles/ === libstdc++ Summary === # of expected passes6036 # of unexpected failures4689 <<< !!! 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-build/547/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/547/artifact/artifacts/sumfiles/xfails.xfail > > 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-build/547/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/546/artifact/artifacts > > Instruction to reproduce the build : > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/c07cf418fdde0c192e370a8d76a991cc7215e9c4/tcwg_gnu_embed_check_gcc/master-thumb_m0_eabi/reproduction_instructions.txt > > Full commit : > https://github.com/gcc-mirror/gcc/commit/c07cf418fdde0c192e370a8d76a991cc7215e9c4 ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
Re: [Linaro-TCWG-CI] 29 patches in glibc: FAIL: 1 regressions on arm
* 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@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 > > | 564bcbe0067 posix: Use in tst-fnmatch3 > | 27a360de01d malloc: Use volatile as compiler barrier in tst-memalign, > tst-valloc > | e24dfc8d9a8 Linux: Optimize getpagesize using > | 3283915ffd0 Install the 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 ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
Re: Buildbot failure - clang-arm64-windows-msvc
Hi Julian, Thanks for reporting this issue. Let me build and test your commit offline and get back to you. -- Omair Javaid www.linaro.org On Sun, 29 Sept 2024 at 03:50, Julian Schmidt wrote: > I decided to revert back to green again. Your insights would be great to > have this patch landed. > > On Sat, 28 Sept 2024 at 12:14, Julian Schmidt < > git.julian.schm...@gmail.com> > wrote: > > > 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/e42cc3f42e6a36f4dfff408278194040367e8259 > > 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 > > > ___ > linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org > To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org > ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
Re: [Linaro-TCWG-CI] gcc-15-3575-gc07cf418fdde: FAIL: 2 regressions on master-thumb_m0_eabi
On Mon, 30 Sept 2024 at 15:36, Christophe Lyon wrote: > > On Mon, 30 Sept 2024 at 10:49, Jonathan Wakely via Gcc-regression > wrote: > > > > On Mon, 30 Sept 2024 at 07:22, 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@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 > > > | 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-build/547/artifact/artifacts/00-sumfiles/ > > > > === libstdc++ Summary === > > > > # of expected passes6036 > > # of unexpected failures4689 <<< !!! > > > > 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. > > > Indeed. > This error was caused by a linker patch of mine, which I've now fixed. Aha, I didn't know if they were longstanding failures or just recent ones. > The CI detected the problem before I pushed my fixed and saw the new > test failing, and reported it as a regression (it has no way of > guessing it's actually a problem with the linker). Gotcha - it's a new failure caused by my patch, so identifying it as a separate regression is of course "correct" in general. > > That being said, we normally start bisection with "new" master branch > (instead of "current" master as of when the regression was detected), > in case it has been fixed between when it was detected and when bisect > actually starts. In this case, I think we had a huge backlog of > regressions to bisect because of my incorrect linker patch, which took > time to recover. Ouch :-) Thanks for the explanations. > Thanks for checking! > > Christophe > > > > > > 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-build/547/artifact/artifacts/notify/ > > > The list of [ignored] baseline and flaky failures are in > > > * > > > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/547/artifact/artifacts/sumfiles/xfails.xfail > > > > > > 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-build/547/artifact/artifacts > > > Reference build : > > > https://ci.linaro.org/job/
Re: [Linaro-TCWG-CI] gcc patch #97864: FAIL: 3 regressions on arm
Hi, Sorry for the delay On Tue, 24 Sept 2024 at 15:17, Jason Merrill wrote: > > On 9/23/24 2:08 AM, ci_not...@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@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 > >| 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/artifact/artifacts/artifacts.precommit/00-sumfiles/ > > 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/artifact/artifacts/artifacts.precommit/notify/ > > The list of [ignored] baseline and flaky failures are in > > - > > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/9301/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail > > Thanks, I believe > https://gcc.gnu.org/pipermail/gcc-patches/2024-September/663711.html > should fix this. IIUC, you committed that followup patch as r15-3858-g2407dbe1d88706, but I'm still seeing these errors in a more recent CI build on aarch64 (r15-3959-g87905f63a6521e) It seems something in your followup patch prevented it from being recognized by patchwork (I can't find it in https://patchwork.sourceware.org/project/gcc/list/, and thus it didn't trigger precommit validation where we could have easily checked that it actually fixed the problem). Thanks, Christophe > > ___ > linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org > To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
Re: [Linaro-TCWG-CI] gcc-15-3575-gc07cf418fdde: FAIL: 2 regressions on master-thumb_m0_eabi
On Mon, 30 Sept 2024 at 10:49, Jonathan Wakely via Gcc-regression wrote: > > On Mon, 30 Sept 2024 at 07:22, 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@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 > > | 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-build/547/artifact/artifacts/00-sumfiles/ > > === libstdc++ Summary === > > # of expected passes6036 > # of unexpected failures4689 <<< !!! > > 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. > Indeed. This error was caused by a linker patch of mine, which I've now fixed. The CI detected the problem before I pushed my fixed and saw the new test failing, and reported it as a regression (it has no way of guessing it's actually a problem with the linker). That being said, we normally start bisection with "new" master branch (instead of "current" master as of when the regression was detected), in case it has been fixed between when it was detected and when bisect actually starts. In this case, I think we had a huge backlog of regressions to bisect because of my incorrect linker patch, which took time to recover. Thanks for checking! Christophe > > > 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-build/547/artifact/artifacts/notify/ > > The list of [ignored] baseline and flaky failures are in > > * > > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/547/artifact/artifacts/sumfiles/xfails.xfail > > > > 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-build/547/artifact/artifacts > > Reference build : > > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/546/artifact/artifacts > > > > Instruction to reproduce the build : > > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/c07cf418fdde0c192e370a8d76a991cc7215e9c4/tcwg_gnu_embed_check_gcc/master-thumb_m0_eabi/reproduction_instructions.txt > > > > Full commit : > > https://github.com/gcc-mirror/gcc/commit/c07cf418fdde0c192e370a8d76a991cc7215e9c4 > ___ linaro-toolchain mailing list -- li
[Linaro-TCWG-CI] binutils-2_41-release-4424-g7ecf0250f7f: FAIL: 1 regressions on arm
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@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 | 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/artifact/artifacts/00-sumfiles/ 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/artifact/artifacts/notify/ The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/1679/artifact/artifacts/sumfiles/xfails.xfail 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/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/1678/artifact/artifacts Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binutils/sha1/7ecf0250f7f0868f3b828ffadd47d0e5f2dbd875/tcwg_binutils_check/master-arm/reproduction_instructions.txt Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=7ecf0250f7f0868f3b828ffadd47d0e5f2dbd875 ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
