Re: [Linaro-TCWG-CI] gcc patch #83662: FAIL: 8 regressions on arm
Hi H.J., Did the email below made it to your inbox? I wonder if some of our precommit CI emails are not reaching developers. Kind regards, -- Maxim Kuvyrkov https://www.linaro.org > On Jan 10, 2024, at 02:24, 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 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-arm after: > > | gcc patch https://patchwork.sourceware.org/patch/83662 > | Author: H.J. Lu > | Date: Tue Jan 9 08:46:59 2024 -0800 > | > | hwasan: Check if Intel LAM_U57 is enabled > | > | When -fsanitize=hwaddress is used, libhwasan will try to enable LAM_U57 > | in the startup code. Update the target check to enable hwaddress tests > | if LAM_U57 is enabled. Also compile hwaddress tests with -mlam=u57 on > | x86-64 since hwasan requires LAM_U57 on x86-64. > | > | ... 3 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 9f7afa99c67 [committed] Adding missing prototype for __clzhi2 to xstormy > port > > FAIL: 8 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/hwasan/hwasan.exp ... > ERROR: can't read "target_hwasan_flags": no such variable > ERROR: tcl error code TCL LOOKUP VARNAME target_hwasan_flags > ERROR: tcl error sourcing g++.dg/hwasan/hwasan.exp. > UNRESOLVED: testcase g++.dg/hwasan/hwasan.exp' aborted due to Tcl error > === gcc tests === > > Running gcc:gcc.dg/hwasan/hwasan.exp ... > ... 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-arm-precommit/5612/artifact/artifacts/artifacts.precommit/00-sumfiles/ > . > The full lists of regressions and progressions are in > - > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/5612/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/5612/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail > . > > The configuration of this build is: > CI config tcwg_gcc_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_gcc_check--master-arm-precommit/5612/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1542/artifact/artifacts ___ 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-14-8168-g14338386970: FAIL: 3 regressions on arm
Hi Nathaniel,
> On Jan 18, 2024, at 13:02, Nathaniel Shead via Gcc-regression
> wrote:
>
> Thanks for the notification! I took a look and the error seems to be
> something specific to the TLS implementation for ARM requiring
> additional flags to link correctly, maybe?
Looking at [1], it seems that only the bare-metal configurations are affected.
And looking at [2], the tests are failing with
===
undefined reference to `__aeabi_read_tp'
===
.
Given that we are configuring GCC for arm-none-eabi with "--enable-threads=no",
the failure is not a surprise.
[1] https://linaro.atlassian.net/browse/GNU-1112
[2]
https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/572/artifact/artifacts/00-sumfiles/g++.log.1.xz
>
> I'm unable to test locally (I don't have access to an ARM machine) but
> from looking at other testsuite examples which make use of thread
> locals, adding the following two lines to the testcases may resolve the
> failures:
>
> // { dg-add-options tls }
> // { dg-require-effective-target tls_runtime }
Yes, this should skip the testcase for targets without thread/TLS support.
>
> Please let me know if the issue is something else and I can take
> another look.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
>
> Yours,
> Nathaniel.
>
> On Thu, Jan 18, 2024 at 07:12:12AM +, 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 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-1112
>> , please let us know if you are looking at the problem and/or when you have
>> a fix.
>>
>> In master-arm_eabi after:
>>
>> | commit gcc-14-8168-g14338386970
>> | Author: Nathaniel Shead
>> | Date: Thu Jan 11 16:49:39 2024 +1100
>> |
>> | c++: Support thread_local statics in header modules [PR113292]
>> |
>> | Currently, thread_locals in header modules cause ICEs. This patch
>> makes
>> | the required changes for them to work successfully.
>> |
>> | This requires additionally writing the DECL_TLS_MODEL for thread-local
>> | variables to the module interface, and the TLS wrapper function needs
>> to
>> | ... 24 lines of the commit log omitted.
>>
>> FAIL: 3 regressions
>>
>> regressions.sum:
>> === g++ tests ===
>>
>> Running g++:g++.dg/modules/modules.exp ...
>> FAIL: g++.dg/modules/pr113292 -std=c++17 link
>> FAIL: g++.dg/modules/pr113292 -std=c++2a link
>> FAIL: g++.dg/modules/pr113292 -std=c++2b link
>>
>> === Results Summary ===
>>
>> You can find the failure logs in *.log.1.xz files in
>> -
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/572/artifact/artifacts/00-sumfiles/
>> .
>> The full lists of regressions and progressions are in
>> -
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/572/artifact/artifacts/notify/
>> .
>> The list of [ignored] baseline and flaky failures are in
>> -
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/572/artifact/artifacts/sumfiles/xfails.xfail
>> .
>>
>> The configuration of this build is:
>> CI config tcwg_gnu_embed_check_gcc master-arm_eabi
>>
>> -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_eabi-build/572/artifact/artifacts
>> Reference build :
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/571/artifact/artifacts
>>
>> Reproduce last good and first bad builds:
>> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/14338386970bc6c2d46b81181f48622fdf25d705/tcwg_gnu_embed_check_gcc/master-arm_eabi/reproduction_instructions.txt
>>
>> Full commit :
>> https://github.com/gcc-mirror/gcc/commit/14338386970bc6c2d46b81181f48622fdf25d705
>>
>> List of configurations that regressed due to this commit :
>> * tcwg_gnu_embed_check_gcc
>> ** master-arm_eabi
>> *** FAIL: 3 regressions
>> ***
>> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/14338386970bc6c2d46b81181f48622fdf25d705/tcwg_gnu_embed_check_gcc/master-arm_eabi/details.txt
>> ***
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/572/artifact/artifacts
___
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro
Re: [Linaro-TCWG-CI] gdb patch #84145: FAIL: 1 regressions: 1 progressions on arm
On 1/16/24 07:42, ci_not...@linaro.org wrote: FAIL: 1 regressions: 1 progressions regressions.sum: === gdb tests === Running gdb:gdb.threads/staticthreads.exp ... FAIL: gdb.threads/staticthreads.exp: up 10 FTR, filed as https://sourceware.org/bugzilla/show_bug.cgi?id=31254 . Thanks, - Tom ___ 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-14-8168-g14338386970: FAIL: 3 regressions on arm
Thanks for the notification! I took a look and the error seems to be
something specific to the TLS implementation for ARM requiring
additional flags to link correctly, maybe?
I'm unable to test locally (I don't have access to an ARM machine) but
from looking at other testsuite examples which make use of thread
locals, adding the following two lines to the testcases may resolve the
failures:
// { dg-add-options tls }
// { dg-require-effective-target tls_runtime }
Please let me know if the issue is something else and I can take
another look.
Yours,
Nathaniel.
On Thu, Jan 18, 2024 at 07:12:12AM +, 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 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-1112 ,
> please let us know if you are looking at the problem and/or when you have a
> fix.
>
> In master-arm_eabi after:
>
> | commit gcc-14-8168-g14338386970
> | Author: Nathaniel Shead
> | Date: Thu Jan 11 16:49:39 2024 +1100
> |
> | c++: Support thread_local statics in header modules [PR113292]
> |
> | Currently, thread_locals in header modules cause ICEs. This patch
> makes
> | the required changes for them to work successfully.
> |
> | This requires additionally writing the DECL_TLS_MODEL for thread-local
> | variables to the module interface, and the TLS wrapper function needs
> to
> | ... 24 lines of the commit log omitted.
>
> FAIL: 3 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.dg/modules/modules.exp ...
> FAIL: g++.dg/modules/pr113292 -std=c++17 link
> FAIL: g++.dg/modules/pr113292 -std=c++2a link
> FAIL: g++.dg/modules/pr113292 -std=c++2b link
>
> === Results Summary ===
>
> You can find the failure logs in *.log.1.xz files in
> -
> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/572/artifact/artifacts/00-sumfiles/
> .
> The full lists of regressions and progressions are in
> -
> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/572/artifact/artifacts/notify/
> .
> The list of [ignored] baseline and flaky failures are in
> -
> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/572/artifact/artifacts/sumfiles/xfails.xfail
> .
>
> The configuration of this build is:
> CI config tcwg_gnu_embed_check_gcc master-arm_eabi
>
> -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_eabi-build/572/artifact/artifacts
> Reference build :
> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/571/artifact/artifacts
>
> Reproduce last good and first bad builds:
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/14338386970bc6c2d46b81181f48622fdf25d705/tcwg_gnu_embed_check_gcc/master-arm_eabi/reproduction_instructions.txt
>
> Full commit :
> https://github.com/gcc-mirror/gcc/commit/14338386970bc6c2d46b81181f48622fdf25d705
>
> List of configurations that regressed due to this commit :
> * tcwg_gnu_embed_check_gcc
> ** master-arm_eabi
> *** FAIL: 3 regressions
> ***
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/14338386970bc6c2d46b81181f48622fdf25d705/tcwg_gnu_embed_check_gcc/master-arm_eabi/details.txt
> ***
> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/572/artifact/artifacts
___
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] glibc-2.38.9000-496-gdf11c05be9: FAIL: 1 regressions on arm
On 18/01/24 10:23, Joseph Myers wrote: > On Thu, 18 Jan 2024, ci_not...@linaro.org wrote: > >> In master-arm after: >> >> | commit glibc-2.38.9000-496-gdf11c05be9 >> | Author: Joseph Myers >> | Date: Wed Jan 17 15:38:54 2024 + >> | >> | Update syscall lists for Linux 6.7 >> | >> | Linux 6.7 adds the futex_requeue, futex_wait and futex_wake syscalls, >> | and enables map_shadow_stack for architectures previously missing it. >> | Update syscall-names.list and regenerate the arch-syscall.h headers >> | with build-many-glibcs.py update-syscalls. >> | >> | ... 1 lines of the commit log omitted. >> >> FAIL: 1 regressions >> >> regressions.sum: >> === glibc tests === >> >> Running glibc:misc ... >> FAIL: misc/tst-glibcsyscalls > > You appear to be testing with some other kernel version with additional > syscalls that are not in the actual 6.7 release. > Yes, we test Linus master branch instead of a specific release. This is not a really a glibc regression, sorry about the noise. ___ 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] glibc-2.38.9000-496-gdf11c05be9: FAIL: 1 regressions on arm
On Thu, 18 Jan 2024, ci_not...@linaro.org wrote: > In master-arm after: > > | commit glibc-2.38.9000-496-gdf11c05be9 > | Author: Joseph Myers > | Date: Wed Jan 17 15:38:54 2024 + > | > | Update syscall lists for Linux 6.7 > | > | Linux 6.7 adds the futex_requeue, futex_wait and futex_wake syscalls, > | and enables map_shadow_stack for architectures previously missing it. > | Update syscall-names.list and regenerate the arch-syscall.h headers > | with build-many-glibcs.py update-syscalls. > | > | ... 1 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === glibc tests === > > Running glibc:misc ... > FAIL: misc/tst-glibcsyscalls You appear to be testing with some other kernel version with additional syscalls that are not in the actual 6.7 release. -- Joseph S. Myers josmy...@redhat.com ___ 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] gdb-14-branchpoint-1244-gfad00902c24: FAIL: 13 regressions: 13 progressions on arm
Hi Thiago, | nm: Replace --with-symbol-versions with --without-symbol-versions in --help output FAIL: 13 regressions: 13 progressions As you're aware, the above are flaky results that the CI wasn't able to filter out as it normally does. Sorry for the false positive. Phew! :-) I ah hoped that that was the case. It seemed strange that changing one line in nm's --help output would generate GDB testsuite failures... Cheers Nick ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
