public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: ci_notify@linaro.org To: tdevries@suse.de Cc: gdb-testers@sourceware.org Subject: [Linaro-TCWG-CI] gdb-15-branchpoint-194-g2f43916ead9: FAIL: 8 regressions: 5 progressions on arm Date: Sat, 15 Jun 2024 04:54:48 +0000 (UTC) [thread overview] Message-ID: <624787686.87482.1718427290149@jenkins.jenkins> (raw) [-- Attachment #1: Type: text/plain, Size: 4278 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-1258 , please let us know if you are looking at the problem and/or when you have a fix. In master-arm after: | commit gdb-15-branchpoint-194-g2f43916ead9 | Author: Tom de Vries <tdevries@suse.de> | Date: Thu Jun 13 17:39:40 2024 +0200 | | [gdb/testsuite] Add gdb.base/fission-macro.exp | | Starting with gcc commit 80048aa13a6 ("debug/111409 - don't generate COMDAT | macro sections for split DWARF"), available from release gcc 14.1 onwards, gcc | produces a usable dwarf-5 32-bit .debug_macro.dwo section. | | Add a test-case excercising this. | ... 4 lines of the commit log omitted. FAIL: 8 regressions: 5 progressions regressions.sum: === gdb tests === Running gdb:gdb.base/fission-macro.exp ... FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32: strict_dwarf=0: info macro FIRST FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32: strict_dwarf=0: info macro FOURTH FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32: strict_dwarf=0: info macro SECOND FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32: strict_dwarf=0: info macro THIRD FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32: strict_dwarf=1: info macro FIRST FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32: strict_dwarf=1: info macro FOURTH FAIL: gdb.base/fission-macro.exp: dwarf_version=5: dwarf_bits=32: strict_dwarf=1: info macro SECOND ... and 2 more entries progressions.sum: === gdb tests === Running gdb:gdb.threads/corethreads.exp ... ERROR: can't read "thread0": no such variable UNRESOLVED: gdb.threads/corethreads.exp: testcase gdb.threads/corethreads.exp' aborted due to Tcl error FAIL: gdb.threads/corethreads.exp: sanity check we see the core file (timeout) ERROR: tcl error code TCL LOOKUP VARNAME thread0 ERROR: tcl error sourcing gdb.threads/corethreads.exp. You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1303/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_gdb--master-arm-build/1303/artifact/artifacts/notify/ The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1303/artifact/artifacts/sumfiles/xfails.xfail The configuration of this build is: CI config tcwg_gnu_native_check_gdb master-arm -----------------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_gdb--master-arm-build/1303/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1302/artifact/artifacts Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/2f43916ead97b183348581e4fd4489cd59845e62/tcwg_gnu_native_check_gdb/master-arm/reproduction_instructions.txt Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=2f43916ead97b183348581e4fd4489cd59845e62 List of configurations that regressed due to this commit : * tcwg_gnu_native_check_gdb ** master-arm *** FAIL: 8 regressions: 5 progressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/2f43916ead97b183348581e4fd4489cd59845e62/tcwg_gnu_native_check_gdb/master-arm/details.txt *** https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1303/artifact/artifacts
reply other threads:[~2024-06-15 4:54 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=624787686.87482.1718427290149@jenkins.jenkins \ --to=ci_notify@linaro.org \ --cc=gdb-testers@sourceware.org \ --cc=linaro-toolchain@lists.linaro.org \ --cc=tdevries@suse.de \ /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).