Hi all,
what should I do with this – I have no idea what artifacts are nor is it
clear to me when looking at the webpage.
Tobias
ci_notify(a)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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> In gcc_check master-aarch64 after:
>
> | gcc patch https://patchwork.sourceware.org/patch/94612
> | Author: Tobias Burnus <tburnus(a)baylibre.com>
> | Date: Fri Jul 26 20:05:43 2024 +0200
> |
> | libgomp: Fix declare target link with offset array-section mapping [PR116107]
> |
> | The main idea of 'link' is to permit putting only a subset of a
> | huge array on the device. Well, in order to make this work properly,
> | it requires that one can map an array section, which does not
> | start with the first element.
> |
> | ... 28 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 6d79d53eed8 Match: Support .SAT_SUB with IMM op for form 1-4
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
> # 2 regressions
>
> From
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-aarch64
>
> -----------------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/7257/art…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2370/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.
Hi Andi,
The regression is ...
=== g++ tests ===
Running g++:g++.dg/dg.exp ...
FAIL: c-c++-common/musttail12.c -std=c++14 (test for excess errors)
FAIL: c-c++-common/musttail12.c -std=c++17 (test for excess errors)
FAIL: c-c++-common/musttail12.c -std=c++20 (test for excess errors)
FAIL: g++.dg/musttail6.C (test for excess errors)
It wasn't included in the report due to typo in the scripts.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 26, 2024, at 19:38, ci_notify(a)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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1299 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-arm after:
>
> | commit gcc-15-2233-g8d1af8f904a
> | Author: Andi Kleen <ak(a)linux.intel.com>
> | Date: Tue Jan 23 23:54:56 2024 -0800
> |
> | Add tests for C/C++ musttail attributes
> |
> | Some adopted from the existing C musttail plugin tests.
> | Also extends the ability to query the sibcall capabilities of the
> | target.
> |
> | gcc/testsuite/ChangeLog:
> | ... 16 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
> # 4 regressions
>
> From
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
>
> -----------------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-arm-build/2460/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2459/artifact/ar…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/8d1af8f904a0c08656d976cbf8ca56dba3…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-arm
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2460/artifact/ar…
Hi Jason,
For this one the regressions are:
=== g++ tests ===
Running g++:g++.dg/dg.exp ...
FAIL: g++.dg/cpp2a/consteval-prop21.C -std=c++20 (test for excess errors)
FAIL: g++.dg/cpp2a/consteval-prop21.C -std=c++23 (test for excess errors)
FAIL: g++.dg/cpp2a/consteval-prop21.C -std=c++26 (test for excess errors)
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 28, 2024, at 09:28, ci_notify(a)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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1301 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-arm after:
>
> | commit gcc-15-2362-ga9e9f772c748
> | Author: Jason Merrill <jason(a)redhat.com>
> | Date: Fri Jul 26 17:20:18 2024 -0400
> |
> | c++: consteval propagation and templates [PR115986]
> |
> | Here the call to e() makes us decide to check d() for escalation at EOF, but
> | while checking it we try to fold_immediate 0_c, and get confused by the
> | template trees. Let's not mess with escalation for function templates.
> |
> | PR c++/115986
> | ... 9 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
> # 3 regressions
>
> From
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
>
> -----------------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-arm-build/2472/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2471/artifact/ar…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/a9e9f772c7488ac0c09dd92f28890bdab9…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-arm
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2472/artifact/ar…
Hi Jason,
The regression is ...
=== g++ tests ===
Running g++:g++.dg/dg.exp ...
FAIL: g++.dg/abi/arm_rtti1.C -std=gnu++26 scan-assembler _ZNKSt9type_infoeqERKS_
It wasn't included in the report due to typo in the scripts.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 28, 2024, at 05:55, ci_notify(a)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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1300 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-arm after:
>
> | commit gcc-15-2360-gdab0f35fcb4d
> | Author: Jason Merrill <jason(a)redhat.com>
> | Date: Fri Jul 26 15:10:50 2024 -0400
> |
> | c++: improve C++ testsuite default versions
> |
> | I wanted to add more cases to the setting of std_list in g++-dg.exp, but
> | didn't want to do a full scan through the file for each case. So this patch
> | improves that in two ways: first, by extracting all interesting lines on a
> | single pass; second, by generating the list more flexibly: now we test every
> | version mentioned explicitly in the testcase, plus a few more if fewer than
> | ... 12 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
> # 1 regressions
>
> From
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
>
> -----------------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-arm-build/2468/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2466/artifact/ar…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/dab0f35fcb4dd3ba584422013096c4ebc6…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-arm
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2468/artifact/ar…
On 2024-07-27 03:34, ci_notify(a)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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> In gdb_check master-aarch64 after:
>
> | 2 patches in gdb
> | Patchwork URL: https://patchwork.sourceware.org/patch/94605
> | 9aca4cc6ec5 gdb: pass inferior to gdbarch_update_p
> | f3b21ad781e gdb: pass inferior to target_current_description
> | ... applied on top of baseline commit:
> | ced7ecee432 Automatic date update in version.in
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe gdb -- --prefix /usr --disable install:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gdb -- --set check_buffer_workaround=gdb-read1:
> 0
> # 1 regressions
>
> From
> # reset_artifacts:
> -10
> # build_abe gdb -- --prefix /usr --disable install:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gdb -- --set check_buffer_workaround=gdb-read1:
> 0
>
> The configuration of this build is:
> CI config tcwg_gdb_check master-aarch64
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/2974/art…
> Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-build/1474/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.
Hello,
Could you help me understand what failed?
Simon
On Mon, Jul 22, 2024 at 02:12:58PM +0000, ci_notify(a)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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/LLVM-1287 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In CI config tcwg_kernel/llvm-master-aarch64-stable-allyesconfig after:
>
> | commit llvmorg-19-init-18145-g1f6f97e2b64a
> | Author: Bill Wendling <5993918+bwendling(a)users.noreply.github.com>
> | Date: Thu Jul 18 22:11:56 2024 +0000
> |
> | [Clang] Loop over FieldDecls instead of all Decls (#99574)
> |
> | Only FieldDecls are important when determining GEP indices. A struct
> | defined within another struct has the same semantics as if it were
> | defined outside of the struct. So there's no need to look into
> | RecordDecls that aren't a field.
> |
> | ... 4 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 22903
>
> From
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 22904
>
> The configuration of this build is:
> CI config tcwg_kernel/llvm-master-aarch64-stable-allyesconfig
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allyescon…
> Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allyescon…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit : https://github.com/llvm/llvm-project/commit/1f6f97e2b64a9c4c51712d32b53e07d…
>
> List of configurations that regressed due to this commit :
> * tcwg_kernel
> ** llvm-master-aarch64-stable-allyesconfig
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
> *** https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allyescon…
This should be fixed with
https://github.com/llvm/llvm-project/commit/6db5f4fd2a287de9d20adc7a44cfcc6….
Cheers,
Nathan
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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1297 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_kernel/gnu-master-aarch64-mainline-allnoconfig after:
| commit gcc-15-2192-g0c5c0c959c2e
| Author: Tamar Christina <tamar.christina(a)arm.com>
| Date: Mon Jul 22 10:28:19 2024 +0100
|
| AArch64: implement TARGET_VECTORIZE_CONDITIONAL_OPERATION_IS_EXPENSIVE [PR115531].
|
| This implements the new target hook indicating that for AArch64 when possible
| we prefer masked operations for any type vs doing LOAD + SELECT or
| SELECT + STORE.
|
| Thanks,
| ... 16 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
662
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
669
# linux build successful:
all
# linux boot successful:
boot
The configuration of this build is:
CI config tcwg_kernel/gnu-master-aarch64-mainline-allnoconfig
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
Full commit : https://github.com/gcc-mirror/gcc/commit/0c5c0c959c2e592b84739f19ca771fa69e…
List of configurations that regressed due to this commit :
* tcwg_kernel
** gnu-master-aarch64-mainline-allnoconfig
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon…