Hi Everyone, Normally, notifications from Linaro TCWG precommit CI are sent only to patch author and patch submitter. In this case the sender was rewritten to "Benjamin Priour via Gcc-patches <gcc-patches@gcc.gnu.org>", which was detected by Patchwork [1] as patch submitter.
Hi Mark, Is "From:" re-write on gcc-patches@ mailing list a side-effect of [2]? I see that some, but not all messages to gcc-patches@ have their "From:" re-written. Also, do you know if re-write of "From:" on gcc-patches@ is expected? [1] https://patchwork.sourceware.org/project/gcc/list/ [2] https://sourceware.org/bugzilla/show_bug.cgi?id=29713 Thanks! -- Maxim Kuvyrkov https://www.linaro.org > On Sep 12, 2023, at 02:58, ci_not...@linaro.org wrote: > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's > #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on > the usual project channel. > > In CI config tcwg_gcc_check/master-aarch64 after: > > | gcc patch https://patchwork.sourceware.org/patch/75674 > | Author: benjamin priour <vultk...@gcc.gnu.org> > | Date: Mon Sep 11 19:44:34 2023 +0200 > | > | analyzer: Move gcc.dg/analyzer tests to c-c++-common (3) [PR96395] > | > | Hi, > | > | Patch below is mostly done, just have to check the formatting. > | Althought, I'd like your feedback on how to manage named_constants > | from enum in C++. > | ... 21 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 048927ed856 i386: Handle CONST_WIDE_INT in output_pic_addr_const [PR111340] > > FAIL: 68 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/analyzer/analyzer.exp ... > FAIL: c-c++-common/analyzer/call-summaries-2.c -std=c++14 (test for excess > errors) > FAIL: c-c++-common/analyzer/call-summaries-2.c -std=c++17 (test for excess > errors) > FAIL: c-c++-common/analyzer/call-summaries-2.c -std=c++20 (test for excess > errors) > FAIL: c-c++-common/analyzer/call-summaries-2.c -std=c++98 (test for excess > errors) > FAIL: c-c++-common/analyzer/memcpy-1.c -std=c++14 (test for warnings, line > 25) > FAIL: c-c++-common/analyzer/memcpy-1.c -std=c++14 (test for warnings, line > 48) > FAIL: c-c++-common/analyzer/memcpy-1.c -std=c++14 (test for excess errors) > ... and 63 more entries > > You can find the failure logs in *.log.1.xz files in > - > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/2244/artifact/artifacts/artifacts.precommit/00-sumfiles/ > . > The full lists of regressions and progressions are in > - > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/2244/artifact/artifacts/artifacts.precommit/notify/ > . > The list of [ignored] baseline and flaky failures are in > - > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/2244/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail > . > > > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/2244/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/927/artifact/artifacts
