On Thu, 10 Oct 2024 at 06:33, <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-1370 , please let us know if you are looking at the problem and/or when you have a fix.
I'm not sure what the problem is here. It looks like the build uses
--enable-clocale=gnu and so I would expect the test to PASS on this
target, like it does on x86_64-pc-linux-gnu. Maybe it's a newlib vs
glibc difference. Looking into it ...
>
> In arm-eabi v7-a softfp after:
>
> | commit gcc-15-4016-gc534e37facc
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Sep 24 23:20:56 2024 +0100
> |
> | libstdc++: Populate std::time_get::get's %c format for C locale
> |
> | We were using the empty string "" for D_T_FMT and ERA_D_T_FMT in the C
> | locale, instead of "%a %b %e %T %Y" as the C standard requires. Set it
> | correctly for each locale implementation that defines time_members.cc.
> | ... 18 lines of the commit log omitted.
>
> FAIL: 1 regressions
> The configuration of this build is:
> CI config tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp
> configure and test flags: --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9
>
> regressions.sum:
> | === libstdc++ tests ===
> |
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 22_locale/time_get/get/wchar_t/5.cc -std=gnu++17 execution test
> |
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
> 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-arm_v7a_softfp_e…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
>
> -----------------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-arm_v7a_softfp_e…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
>
> 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/c534e37faccf481afa9bc28f0605ca0ec3…
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-1365 , please let us know if you are looking at the problem and/or when you have a fix.
In glibc_check master-arm after:
| commit glibc-2.40.9000-226-g42c810c2cf3
| Author: Joseph Myers <josmyers(a)redhat.com>
| Date: Mon Oct 7 19:44:25 2024 +0000
|
| Add freopen special-case tests: thread cancellation
|
| Add tests of freopen adding or removing "c" (non-cancelling I/O) from
| the mode string (so completing my planned tests of freopen with
| different features used in the mode strings). Note that it's in the
| ... 5 lines of the commit log omitted.
FAIL: 1 regressions
The configuration of this build is:
CI config tcwg_glibc_check master-arm
configure and test flags: --target arm-linux-gnueabihf
regressions.sum:
| === glibc tests ===
|
| Running glibc:. ...
| FAIL: lint-makefiles
|
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1894/artifact/…
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=42c810c2cf3554afbdd6…
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/LLVM-1379 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_flang_build/main-aarch64 after:
| commit llvmorg-20-init-8106-ge36a39346796
| Author: Matthias Springer <me(a)m-sp.org>
| Date: Sat Oct 5 21:46:31 2024 +0200
|
| [mlir][SPIRV] Fix build error (#111264)
|
| Fix build error that was introduced by #111250. Also, the deleted
| function is not needed at all.
|
| ... 9 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# true:
0
# build_llvm -- clang;lld;flang;openmp;clang-tools-extra :
# FAILED
From
# reset_artifacts:
-10
# true:
0
# build_llvm -- clang;lld;flang;openmp;clang-tools-extra :
1
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/1063/artifac…
Reference build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/1062/artifac…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
Full commit : https://github.com/llvm/llvm-project/commit/e36a39346796528f75ff01ef1084b2d…
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
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…
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.
* 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
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