From: Mark Wielaard <mark@klomp.org>
To: Stan Cox <scox@redhat.com>
Cc: Frysk Hackers <frysk@sourceware.org>
Subject: Re: avoid fc5 kernels > kernel-2.6.17-1.2187_FC5 and < 1.2243
Date: Wed, 22 Nov 2006 11:59:00 -0000 [thread overview]
Message-ID: <1164196740.3084.32.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <1164140417.13567.110.camel@multics.rdu.redhat.com>
Hi Stan,
On Tue, 2006-11-21 at 15:20 -0500, Stan Cox wrote:
> On Tue, 2006-11-21 at 18:24 +0100, Mark Wielaard wrote:
>
> > 1) testExecSyscall(frysk.proc.TestTaskSyscallObserver)
This one seems not deterministic although it fails most of the time for
me. This is http://sourceware.org/bugzilla/show_bug.cgi?id=3244
> Running testLinuxIa32(frysk.proc.TestSyscallsWithAudit) ...FAIL
> Running testLinuxPPC(frysk.proc.TestSyscallsWithAudit) ...FAIL
> Running testLinuxPPC64(frysk.proc.TestSyscallsWithAudit) ...FAIL
> Running testLinuxX86_64(frysk.proc.TestSyscallsWithAudit) ...FAIL
These do pass for me on a similar system. What version of libaudit do
you have? $ rpm -q audit-libs
audit-libs-1.2.9-1.fc5
audit-libs-1.2.9-1.fc5
(Apparently I have both the i386 and x86_64 versions installed)
> Running testMultiThreadedDetached(frysk.util.TestFStack) ...FAIL
> Running testMultiThreadedAckDaemon(frysk.util.TestFStack) ...FAIL
> Running testStressMultiThreadedDetach(frysk.util.TestFStack) ...FAIL
> Running testClone(frysk.util.TestFStack) ...FAIL
So these are common failures for x86_64, but not on x86. FStack probably
tries to match the call stack precisely to what is generated on x86.
Cheers,
Mark
prev parent reply other threads:[~2006-11-22 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 7:51 Roland McGrath
2006-11-21 17:24 ` Mark Wielaard
2006-11-21 20:22 ` Stan Cox
2006-11-22 11:59 ` Mark Wielaard [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=1164196740.3084.32.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=scox@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).