From: Andrew Cagney <cagney@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk@sourceware.org
Subject: Re: What does brokenIfUtraceXXX() test for?
Date: Wed, 04 Jul 2007 19:19:00 -0000 [thread overview]
Message-ID: <468BF2AF.9070704@redhat.com> (raw)
In-Reply-To: <1183392408.3622.24.camel@dijkstra.wildebeest.org>
See bug 3639. Seems fixing it slipped through the cracks, I
fixed/closed the bug. 3489 contains a hidden references 3639 in one of
the comments; I've also made that more obvious.
As for brokenIfUtraceXXX, be careful to not read anything into it. The
test has an unresolved problem, see BUG XXXXX :-)
Mark Wielaard wrote:
> Hi,
>
> I am seeing two failures on 2.6.21-1.3228.fc7 x86 SMP:
>
> testTerminateKillKILL(frysk.proc.TestTaskTerminateObserver)junit.framework.AssertionFailedError: terminating value expected:<-9> but was:<128>
> testTerminatingKillKILL(frysk.proc.TestTaskTerminateObserver)junit.framework.AssertionFailedError: terminating value expected:<-9> but was:<128>
>
> That are guarded by brokenIfUtraceXXX() which has as explanation:
>
> /**
> * A method that returns true, and prints broken, when the build
> * kernel includes UTRACE.
> */
>
> So, tests guarded by that ever never expected to succeed with utrace
> enabled? Or is it more subtle than that? Both bugs referenced through
> these guards (#3525 and #3489) are closed already.
>
> Cheers,
>
> Mark
>
>
prev parent reply other threads:[~2007-07-04 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 16:06 Mark Wielaard
2007-07-04 19:19 ` Andrew Cagney [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=468BF2AF.9070704@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.org \
/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).