public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/5668] New: frysk.sys.TestSignalSet failures
Date: Fri, 25 Jan 2008 11:38:00 -0000 [thread overview]
Message-ID: <20080125113722.5668.mark@klomp.org> (raw)
One of the recent Signal changes made these two tests fail.
It looks like something simple in the string representation changed that caused
these errors. But it would be good if someone more familiar with the Signal
changes could take a look.
There were 2 failures:
1) testSingleToString(frysk.sys.TestSignalSet)junit.framework.ComparisonFailure:
SIGHUP set expected:<......> but was:<...(1)...>
at frysk.sys.TestSignalSet.testSingleToString(TestRunner)
at frysk.junit.Runner.runCases(TestRunner)
at frysk.junit.Runner.runTestCases(TestRunner)
at TestRunner.main(TestRunner)
2) testMultiToString(frysk.sys.TestSignalSet)junit.framework.ComparisonFailure:
SIGHUP+SIGUSR1 set expected:<...,SIGUSR1...> but was:<...(1),SIGUSR1(10)...>
at frysk.sys.TestSignalSet.testMultiToString(TestRunner)
at frysk.junit.Runner.runCases(TestRunner)
at frysk.junit.Runner.runTestCases(TestRunner)
at TestRunner.main(TestRunner)
--
Summary: frysk.sys.TestSignalSet failures
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: mark at klomp dot org
CC: cagney at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=5668
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-01-25 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 11:38 mark at klomp dot org [this message]
2008-01-25 14:28 ` [Bug general/5668] " cagney at redhat dot com
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=20080125113722.5668.mark@klomp.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=frysk-bugzilla@sourceware.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).