Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Remove pass in skip_unwinder_tests
Date: Mon, 27 Aug 2012 13:07:00 -0000	[thread overview]
Message-ID: <20120827130641.GA5592@host2.jankratochvil.net> (raw)
In-Reply-To: <503B4CF7.5090509@codesourcery.com>

On Mon, 27 Aug 2012 12:33:27 +0200, Yao Qi wrote:
> On 08/25/2012 12:18 AM, Jan Kratochvil wrote:
> >If the system does not have unwinder hook it will XFAIL.  XFAIL is not even
> >displayed on screen during interactive run.
> 
> If we do a gdb test, and test is failed because of the misbehaviour,
> we should use XFAIL.

What is "misbehavior" here?


> However, in proc 'skip_XXX' in lib/gdb.exp, we
> check the supported feature of system instead of doing a gdb test,
> so no PASS/FAIL/XFAIL should be emitted.

XFAIL is for "unsupported system feature".

What does XFAIL mean different than "unsupported system feature"?

When will ever be XFAIL emitted if not for "unsupported system feature"?


THanks,
Jan


  reply	other threads:[~2012-08-27 13:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 16:20 RFC: consolidate checks for _Unwind_DebugHook in test suite Tom Tromey
2012-08-15  0:53 ` Yao Qi
2012-08-15 13:58   ` Tom Tromey
2012-08-22 14:26 ` Tom Tromey
2012-08-23  9:50 ` [PATCH 1/2] Append "." in error message Yao Qi
2012-08-23  9:50   ` [PATCH 2/2] Remove pass in skip_unwinder_tests Yao Qi
2012-08-23 10:52     ` Pedro Alves
2012-08-23 12:29       ` Yao Qi
2012-08-23 18:03         ` Pedro Alves
2012-08-24 13:38     ` Jan Kratochvil
2012-08-24 15:41       ` Pedro Alves
2012-08-24 16:19         ` Jan Kratochvil
2012-08-24 16:53           ` Pedro Alves
2012-08-24 16:57             ` Pedro Alves
2012-08-24 17:12             ` Jan Kratochvil
2012-08-27 10:33           ` Yao Qi
2012-08-27 13:07             ` Jan Kratochvil [this message]
2012-08-27 15:15               ` Yao Qi
2012-08-27 15:57                 ` Jan Kratochvil
2012-08-24 13:34   ` [PATCH 1/2] Append "." in error message Jan Kratochvil
2012-08-24 13:40 ` RFC: consolidate checks for _Unwind_DebugHook in test suite Jan Kratochvil
2012-08-24 13:54   ` Tom Tromey
2012-08-24 14:08     ` Jan Kratochvil
2012-08-24 15:26       ` Tom Tromey

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=20120827130641.GA5592@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=yao@codesourcery.com \
    /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: link
Be 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