On 2025-01-09 12:16, ci_not...@linaro.org wrote:
> Dear contributor,
> 
> Our automatic CI has detected problems related to your patch(es). Please find 
> some details below.
> 
> In glibc_build master-aarch64, after:
>   | 8 patches in glibc
>   | Patchwork URL: https://patchwork.sourceware.org/patch/104425
>   | b2d4876946 [PATCH v16 8/8] Linux: Update internal copy of '<sys/rseq.h>'
>   | cdd3e61830 [PATCH v16 7/8] nptl: Remove the rseq area from 'struct 
> pthread'
>   | a673377e3d [PATCH v16 6/8] nptl: Move the rseq area to the 'extra TLS' 
> block
>   | 86803776b0 [PATCH v16 5/8] nptl: Introduce <rseq-access.h> for RSEQ_* 
> accessors
>   | 928c07fc09 [PATCH v16 4/8] nptl: add rtld_hidden_proto to __rseq_size and 
> __rseq_offset
>   | ... and 3 more patches in glibc
>   | ... applied on top of baseline commit:
>   | e41aabcc93 tests: Verify inheritance of cpu affinity
> 
> Produces Failure:
>   | Results changed to
>   | # reset_artifacts:
>   | -10
>   | # init_abe_sysroot:
>   | 0
>   | # build_abe glibc -- --disable install:
>   | # FAILED
>   | # First few build errors in logs:
>   | # 00:00:59 ../csu/libc-tls.c:221:64: error: ‘TLS_TP_OFFSET’ undeclared 
> (first use in this function); did you mean ‘TLS_DTV_OFFSET’?
>   | # 00:00:59 make[2]: *** 
> [/home/tcwg-build/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/sysd-rules:451:
>  
> /home/tcwg-build/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/csu/libc-tls.o]
>  Error 1
>   | # 00:00:59 make[1]: *** [Makefile:484: csu/subdir_lib] Error 2
>   | # 00:00:59 make: *** [Makefile:20: all] Error 2

Is there a way to re-trigger this job on the current master branch without 
posting a new patchset?

I sent this by mistake before Florian's TLS_TP_OFFSET patch was pushed to 
master but it is now.

Thanks,

Michael

_______________________________________________
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org

Reply via email to