On Mon, Jun 9, 2025 at 10:02 PM ci_notify@linaro.org wrote:
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_check master-aarch64, after: | glibc patch https://patchwork.sourceware.org/patch/113987 | Author: H.J. Lu hjl.tools@gmail.com | Date: Mon Jun 9 05:22:10 2025 +0800 | | [PATCH] i386: Update ___tls_get_addr to preserve vector registers | | Compiler generates the following instruction sequence for dynamic TLS | access: | | ... 44 lines of the commit log omitted. | ... applied on top of baseline commit: | 0a027674a10 x86: Avoid GLRO(dl_x86_cpu_features)
Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-tls23
So, this is a run-time failure. What happens if you run it by hand?
Used configuration : *CI config* tcwg_glibc_check master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
The full lists of regressions and improvements as well as configure and make commands are in
The list of [ignored] baseline and flaky failures are in
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/3701/ar... Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2930/artifa...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.