Hello!
On 03.04.2025 14:32, ci_notify@linaro.org wrote:
Our automatic CI has detected problems related to your patch(es). Please find some details below.
Could you please help me understand what the detected problem(s) are? The mail subject suggests that everything may actually be fine?
In binutils_build master-arm, after: | 5 patches in binutils | Patchwork URL: https://patchwork.sourceware.org/patch/109718 | cde90675110 [PATCH 5/8] s390: Represent FP without RA saved in SFrame | fa5be46ad1a [PATCH 4/8] s390: Represent FP/RA saved in register in SFrame | b029a0bbe60 [PATCH 3/8] s390: Initial support to generate .sframe from CFI directives in assembler | d40f1518ae8 [PATCH 2/8] s390: Explicitly list linker dump tests | 45da7966615 [PATCH 1/8] sframe: Ignore section padding when converting endianness | ... applied on top of baseline commit: | abf215a338f ld/testsuite/ld-pe: Escape dots in regular expressions
My series consists of 8 patches. Could it be that they appeared in Patchworks in a bad order, e.g. due to in what order my company's mail server delivered them to the list, and this now confuses the CI?
https://patchwork.sourceware.org/project/binutils/list/?series=45805
Produces Success: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1
The results appear to be unchanged to me.
Used configuration : *CI config* tcwg_binutils_build master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
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
The full lists of regressions and improvements as well as configure and make commands are in
Current build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-precommit/3765/art... Reference build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-build/2375/artifac...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.
Thanks and regards, Jens
On Thu, 3 Apr 2025 at 14:50, Jens Remus jremus@linux.ibm.com wrote:
Hello!
On 03.04.2025 14:32, ci_notify@linaro.org wrote:
Our automatic CI has detected problems related to your patch(es). Please find some details below.
Could you please help me understand what the detected problem(s) are? The mail subject suggests that everything may actually be fine?
Hi!
Normally we do not send notifications when the regression tests pass (which is the case here).
Unfortunately I introduced a typo in a script, and we sent the template notification.
Should be fixed soon.
Sorry for the inconvenience.
Christophe
In binutils_build master-arm, after: | 5 patches in binutils | Patchwork URL: https://patchwork.sourceware.org/patch/109718 | cde90675110 [PATCH 5/8] s390: Represent FP without RA saved in SFrame | fa5be46ad1a [PATCH 4/8] s390: Represent FP/RA saved in register in SFrame | b029a0bbe60 [PATCH 3/8] s390: Initial support to generate .sframe from CFI directives in assembler | d40f1518ae8 [PATCH 2/8] s390: Explicitly list linker dump tests | 45da7966615 [PATCH 1/8] sframe: Ignore section padding when converting endianness | ... applied on top of baseline commit: | abf215a338f ld/testsuite/ld-pe: Escape dots in regular expressions
My series consists of 8 patches. Could it be that they appeared in Patchworks in a bad order, e.g. due to in what order my company's mail server delivered them to the list, and this now confuses the CI?
https://patchwork.sourceware.org/project/binutils/list/?series=45805
Produces Success: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1
The results appear to be unchanged to me.
Used configuration : *CI config* tcwg_binutils_build master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
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
The full lists of regressions and improvements as well as configure and make commands are in
Current build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-precommit/3765/art... Reference build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-build/2375/artifac...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.
Thanks and regards, Jens -- Jens Remus Linux on Z Development (D3303) +49-7031-16-1128 Office jremus@de.ibm.com
IBM
IBM Deutschland Research & Development GmbH; Vorsitzender des Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294 IBM Data Privacy Statement: https://www.ibm.com/privacy/
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-leave@lists.linaro.org
linaro-toolchain@lists.linaro.org
-
Christophe Lyon -
Jens Remus