public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "maxim.kuvyrkov at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug external/31410] [gdb/Linaro CI progression] FAIL: gdb.base/startup-with-shell.exp: startup_with_shell = off; run_args = *.unique-extension: first argument not expanded Date: Mon, 26 Feb 2024 13:10:33 +0000 [thread overview] Message-ID: <bug-31410-4717-q3jfWW3foK@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31410-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31410 Maxim Kuvyrkov <maxim.kuvyrkov at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxim.kuvyrkov at gmail dot com --- Comment #1 from Maxim Kuvyrkov <maxim.kuvyrkov at gmail dot com> --- Hi Tom, Yes, this annoys me as well, but the problem is a bit more complicated. Our CI automatically updates xfails file, which includes both failed test in the baseline and flaky tests. The problem with this test, is that it consistently fails in our post-commit CI jobs, but tends to pass in the pre-commit jobs. Since we are using baseline results from the post-commit CI to compare pre-commit CI results against -- we get this "progression". We have it on our TODO list to fix this problem, but it requires digging into the GDB testsuite logic to understand where the different behavior is coming from. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-26 13:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-24 9:04 [Bug external/31410] New: " vries at gcc dot gnu.org 2024-02-24 9:04 ` [Bug external/31410] " vries at gcc dot gnu.org 2024-02-26 13:10 ` maxim.kuvyrkov at gmail dot com [this message] 2024-02-26 14:02 ` [Bug testsuite/31410] [gdb/testsuite] " vries at gcc dot gnu.org 2024-02-26 14:14 ` tromey at sourceware dot org 2024-02-26 14:17 ` vries at gcc dot gnu.org 2024-02-26 14:59 ` cvs-commit at gcc dot gnu.org 2024-02-26 15:01 ` vries at gcc dot gnu.org 2024-02-26 15:14 ` thiago.bauermann at linaro dot org
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=bug-31410-4717-q3jfWW3foK@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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).