From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CEEA4383236E; Tue, 15 Nov 2022 10:53:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CEEA4383236E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1668509590; bh=Ezm7P5QmEqaY1R0z4T0aDbPxZKpTT341roCykFU4AXQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=M5c/P47pto+Kiwaf80JYd92I/xOJ1/F8EatvpDUmDGuGkpHbsG0YsuxHaMvB1hezg KrvrmJZFT4pb/N767Q8Q74zE9J+pZ6itz0ViTOjUNBHYiTi2I7+gvBHsQfIDf364qL SRcVFOQ2LbE87yBz7OOEyaML1EzxD5dAILrD4SHk= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/29778] [gdb/testsuite] Revise untested usage Date: Tue, 15 Nov 2022 10:53:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: vries at gcc dot gnu.org 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: 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=3D29778 --- Comment #1 from Tom de Vries --- Hmm, reading the definition of UNSUPPORTED: ... There is no support for the tested case. This may mean that a conditional feature of an operating system, or of a compiler, is not implemented. DejaG= nu also uses this message when a testing environment (often a =E2=80=9Cbare bo= ard=E2=80=9D target) lacks basic support for compiling or running the test case. For example, a = test for the system subroutine gethostname would never work on a target board running only a boot monitor. ... and seeing how like XFAIL it's focused on the environment, I start to wonde= r if the role of UNTESTED was intended to be that it's to UNSUPPORTED what KFAIL= is to XFAIL. In other words: - xfail: fail due to problem in environment - kfail: fail due to problem in gdb - unsupported: not run due to missing optional feature in environment - untested: not run due to missing optional feature in gdb That way, each one implies one type of action to achieve a passing test-cas= e: - xfail: fix environment - kfail: fix gdb - unsupported: add missing feature to environment - untested: build gdb with missing feature enabled --=20 You are receiving this mail because: You are on the CC list for the bug.=