From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14427 invoked by alias); 15 Dec 2011 05:22:03 -0000 Received: (qmail 14415 invoked by uid 22791); 15 Dec 2011 05:22:02 -0000 X-SWARE-Spam-Status: No, hits=-3.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 15 Dec 2011 05:21:49 +0000 Received: from eliz by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1Rb3lK-0007dC-Ld; Thu, 15 Dec 2011 00:21:46 -0500 Date: Thu, 15 Dec 2011 05:33:00 -0000 Message-Id: From: Eli Zaretskii To: Jan Kratochvil CC: dje@google.com, brobecker@adacore.com, tromey@redhat.com, gdb-patches@sourceware.org In-reply-to: <20111214194220.GA24281@host2.jankratochvil.net> (message from Jan Kratochvil on Wed, 14 Dec 2011 20:42:20 +0100) Subject: Re: [doc patch] gdbint: XFAIL vs. KFAIL [Re: [patch] gcc KFAILs to XFAILs] Reply-to: Eli Zaretskii References: <20111209171630.GA30059@host2.jankratochvil.net> <20111209171937.GA30594@host2.jankratochvil.net> <20111209215319.GA5132@host2.jankratochvil.net> <20111210160145.GA7261@host2.jankratochvil.net> <20111211024742.GN21915@adacore.com> <20111211092552.GA14574@host2.jankratochvil.net> <20111211124213.GO21915@adacore.com> <20111214185650.GA8485@host2.jankratochvil.net> <20111214194220.GA24281@host2.jankratochvil.net> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-12/txt/msg00495.txt.bz2 > Date: Wed, 14 Dec 2011 20:42:20 +0100 > From: Jan Kratochvil > Cc: Joel Brobecker , Tom Tromey , gdb-patches@sourceware.org > > On Wed, 14 Dec 2011 20:28:15 +0100, Doug Evans wrote: > > Can someone check into gdbint.texi definitions of xfail and kfail? > > There's a section "Writing Tests", seems like an appropriate place. > > FYI I wanted to add it to > http://sourceware.org/gdb/wiki/GDBTestcaseCookbook > but it already states: > Known failing new testcases must produce KFAIL (GDB problem) or XFAIL > (environment problem). > > Not going to check it in without the doc review. This is okay, but I have one suggestion: > +Known problem of @value{GDBN} itself. You must specify the @value{GDBN} bug > +report number. Regarding the "must specify the bug report number": would it make sense to show how to do that, e.g. with an example? Thanks.