public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: ci_notify@linaro.org To: tom@tromey.com Cc: gdb-testers@sourceware.org Subject: [Linaro-TCWG-CI] gdb-14-branchpoint-2123-g4e417d7bb1c: FAIL: 3 regressions on aarch64 Date: Wed, 17 Apr 2024 23:39:50 +0000 (UTC) [thread overview] Message-ID: <2020403791.19322.1713397192466@jenkins.jenkins> (raw) [-- Attachment #1: Type: text/plain, Size: 3388 bytes --] 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@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-1202 , please let us know if you are looking at the problem and/or when you have a fix. In master-aarch64 after: | commit gdb-14-branchpoint-2123-g4e417d7bb1c | Author: Tom Tromey <tom@tromey.com> | Date: Fri Jan 12 18:01:00 2024 -0700 | | Change handling of DW_TAG_enumeration_type in DWARF scanner | | Currently the DWARF scanner will enter enumeration constants into the | same namespace as the DW_TAG_enumeration_type itself. This is the | right thing to do, but the implementation may result in strange | entries being added to the addrmap that maps DIE ranges to entries. | | ... 8 lines of the commit log omitted. FAIL: 3 regressions regressions.sum: === libstdc++ tests === Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ... FAIL: libstdc++-prettyprinters/debug.cc print redirected FAIL: libstdc++-prettyprinters/simple.cc print redirected FAIL: libstdc++-prettyprinters/simple11.cc print redirected You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1069/artifact/artifacts/00-sumfiles/ The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1069/artifact/artifacts/notify/ The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1069/artifact/artifacts/sumfiles/xfails.xfail The configuration of this build is: CI config tcwg_gnu_native_check_gcc master-aarch64 -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1069/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1068/artifact/artifacts Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/4e417d7bb1c7d8b8a73b73b0b7c051f0a6e1b6b6/tcwg_gnu_native_check_gcc/master-aarch64/reproduction_instructions.txt Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=4e417d7bb1c7d8b8a73b73b0b7c051f0a6e1b6b6 List of configurations that regressed due to this commit : * tcwg_gnu_native_check_gcc ** master-aarch64 *** FAIL: 3 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/4e417d7bb1c7d8b8a73b73b0b7c051f0a6e1b6b6/tcwg_gnu_native_check_gcc/master-aarch64/details.txt *** https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1069/artifact/artifacts
next reply other threads:[~2024-04-17 23:39 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-17 23:39 ci_notify [this message] 2024-04-22 1:02 ` Christophe Lyon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=2020403791.19322.1713397192466@jenkins.jenkins \ --to=ci_notify@linaro.org \ --cc=gdb-testers@sourceware.org \ --cc=linaro-toolchain@lists.linaro.org \ --cc=tom@tromey.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).