From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 89EC43895FF7; Tue, 15 Nov 2022 14:35:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 89EC43895FF7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1668522951; bh=G8B4u10VNJvmqXS1GxCV088cnaL7HM06g62w9IPfqJk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=WEX8qpu+q9JXJfz4P28/KAVESJbCiVJ3BJFiHjk927DjUwz012ZuAA022iCeBB8BQ gBY4MIjuVmx78NJRF6cx2q8gZhUbn3UohpAfBaJv1rtfjTYA0Mz+LWFfgCR9Y0NE/R 4L5pJrrQnE8ool6NqqyGSIC+3q81Aw5ZhpiM4qMc= From: "simon.marchi at polymtl dot ca" To: gdb-prs@sourceware.org Subject: [Bug testsuite/29778] [gdb/testsuite] Revise untested usage Date: Tue, 15 Nov 2022 14:35:51 +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: simon.marchi at polymtl dot ca 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=3D29778 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at polymtl do= t ca --- Comment #3 from Simon Marchi --- (In reply to Tom de Vries from comment #1) > 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. Dej= aGnu > also uses this message when a testing environment (often a =E2=80=9Cbare = board=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 won= der > if the role of UNTESTED was intended to be that it's to UNSUPPORTED what > KFAIL is to XFAIL. >=20 > 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 I'm struggling a bit with the difference between unsupported and untested, especially because unsupported sounds like a specific case of untested. And except because of what the Dejagnu documentation says, unsupported really sounds like it could be used for both "missing feature in environment" and "missing feature in gdb". Using unsupported just for the former one seems arbitrary. > And then there are the test-cases that use proc skip_ variants which larg= ely seem happy to skip only doing "verbose $msg" or just silently. I think all tests should at least record at least one untested or unsupport= ed, so that there's a trace in gdb.sum. --=20 You are receiving this mail because: You are on the CC list for the bug.=