On Tue, Jan 28, 2025 at 10:32 AM Jerry D <jvdelis...@gmail.com> wrote: > > > Before I go clicking on links, is this legit? I presume patches are > getting checked before being pushed.
Yes this is a legit email from the Linaro automation. And yes patches are being tested before they get pushed to help developers just in case things like this are missed. I don't see why arm would be different from any other target here though and why it is failing for arm only. Thanks, Andrew > > I do not have an arm based machine to test on. > > Regards, > > Jerry > > -------- Forwarded Message -------- > Subject: [Linaro-TCWG-CI] gcc patch #105542: 12 regressions on arm > Date: Tue, 28 Jan 2025 11:04:22 +0000 (UTC) > From: ci_not...@linaro.org > Reply-To: linaro-toolch...@lists.linaro.org > To: jvdelis...@gmail.com > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please > find some details below. > > In gcc_check master-arm, after: > | gcc patch https://patchwork.sourceware.org/patch/105542 > | Author: Jerry D <jvdelis...@gmail.com> > | Date: Mon Jan 27 19:41:04 2025 -0800 > | | [patch, libfortran] PR114618 Format produces incorrect > output when contains 1x, ok when uses " " > | | Hello all, > | | The attached patch is part 1 of my effort to fix these > X and T edit > | ... 58 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 846f08623b4 Remove ChangeLog entry that shouldn't be there. > > Produces 12 regressions: > | | regressions.sum: > | Running gfortran:gfortran.dg/dg.exp ... > | FAIL: gfortran.dg/char4_iunit_2.f03 -O0 execution test > | FAIL: gfortran.dg/char4_iunit_2.f03 -O1 execution test > | FAIL: gfortran.dg/char4_iunit_2.f03 -O2 execution test > | FAIL: gfortran.dg/char4_iunit_2.f03 -O3 -fomit-frame-pointer > -funroll-loops -fpeel-loops -ftracer -finline-functions execution test > | ... and 8 more > > Used configuration : > *CI config* tcwg_gcc_check master-arm > *configure and test flags:* --target arm-linux-gnueabihf > > If you have any questions regarding this report, please ask on > linaro-toolch...@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_check--master-arm-precommit/10959/artifact/artifacts/artifacts.precommit/00-sumfiles/ > The full lists of regressions and improvements as well as configure and > make commands are in > * > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10959/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/10959/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10959/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3353/artifact/artifacts > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.
