From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8C2043858C54; Mon, 26 Feb 2024 13:10:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8C2043858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1708953034; bh=q5xwynZY6yzsHDJRaQsWOohM7f6Y/bZEfguWqantBfE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=S7AL1CifT+K+/7uKhSdBDoEl/GJb5eegIKDWPfEtT4X252nNFhs/gJk9uW8p8SFO1 OnJ+JvbjiBBxhjGwsE2LJ6YZw4arxrWpCmDpfXBukZSk18mBysOTzV3YJ/payB6Nc6 9NDZ1fAQEFQK9U5lPOecNWiXCjAnU2YLTOjv2Gfg= From: "maxim.kuvyrkov at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: external X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: maxim.kuvyrkov at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31410 Maxim Kuvyrkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxim.kuvyrkov at gmail do= t com --- Comment #1 from Maxim Kuvyrkov --- Hi Tom, Yes, this annoys me as well, but the problem is a bit more complicated. Ou= r 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-commi= t 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 in= to the GDB testsuite logic to understand where the different behavior is coming from. --=20 You are receiving this mail because: You are on the CC list for the bug.=