From: fche@redhat.com (Frank Ch. Eigler)
To: William Cohen <wcohen@redhat.com>
Cc: systemTAP <systemtap@sources.redhat.com>
Subject: Re: KFAIL tests in testsuite
Date: Thu, 31 Jan 2008 19:01:00 -0000 [thread overview]
Message-ID: <y0mk5lpzuos.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <47A0DDCB.1090303@redhat.com> (William Cohen's message of "Wed, 30 Jan 2008 15:27:55 -0500")
William Cohen <wcohen@redhat.com> writes:
> I am looking through and appropriately markiung tests that fail due to
> known reasons as KFAIL. So something like the attached patch.
This one is fine.
> The one concern that I have about marking some tests as KFAIL is
> that failure may vary on the environment. Some versions of
> supporting software or kernels may cause a test to fail. However,
> the test doesn't uniformly fail. [...]
Right, though if this becomes a problem (so one can't tell whether
one's dealing with something new), then one can conditionalize the
setup_kfail clauses further, based on architecture, versions, and
maybe even a bit of whatnot(tm).
- FChE
prev parent reply other threads:[~2008-01-31 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 20:28 William Cohen
2008-01-31 19:01 ` Frank Ch. Eigler [this message]
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=y0mk5lpzuos.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=wcohen@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).