Hello,
I seem to have begun receiving CI/CD patch notifications from ci_notify@linaro.org. I don't understand them, and they might be premature. I don't want to ignore them, though, if they do matter.
I am supplying a 100,000 line patch, roughly, to add a COBOL front-end to gcc. As of now, there is no libgcobol or gcc/cobol directory in the master branch. The supplied patch came most recently in 14 "easy pieces". To be applied successfully, the patches to the Python scripts that create those directories must be applied first.
The URLs at the end of the mail come up 404. I suppose they are ephemeral. I haven't been able to look at a complete log to understand the basis of the report.
The mail says to ask here, so here I be. Please advise. I'm not subscribed to this list.
Thanks,
--jkl
Begin forwarded message:
Date: Wed, 19 Feb 2025 15:10:38 +0000 (UTC) From: ci_notify@linaro.org To: jklowden@schemamania.org Subject: [Linaro-TCWG-CI] gcc patch #106762: Failure on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In gcc_build master-aarch64, after: | gcc patch https://patchwork.sourceware.org/patch/106762 | Author: James K. Lowden jklowden@schemamania.org | Date: Tue Feb 18 18:37:13 2025 -0500 | | [PATCH] COBOL v3: 3/14 80K bld: config and build machinery | | From f89a50238de62b73d9fc44ee7226461650ab119d Tue 18 Feb 2025 04:19:10 PM EST | From: "James K. Lowden" jklowden@symas.com | Date: Tue 18 Feb 2025 04:19:10 PM EST | ... 27 lines of the commit log omitted. | ... applied on top of baseline commit: | 427386042f0 LoongArch: Use normal RTL pattern instead of UNSPEC for {x,}vsr{a,l}ri instructions
Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe gcc: | # FAILED | # First few build errors in logs: | # 00:03:17 make[1]: *** [Makefile:4720: all-gcc] Error 2 | # 00:03:17 make: *** [Makefile:1063: all] Error 2 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe gcc: | 1
Used configuration : *CI config* tcwg_gcc_build master-aarch64 *configure and test flags:*
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 * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/art... The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/art... The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/art...
Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/art... Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3164/artifact...
Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.