This is the mail archive of the
frysk@sources.redhat.com
mailing list for the frysk project.
Fwd: [Bug general/3014] New: TestRunner hang at testTaskForkedObserver, after some ERRORs and FAILs
- From: Wu Zhou <woodzltc at cn dot ibm dot com>
- To: frysk at sources dot redhat dot com
- Date: Tue, 8 Aug 2006 23:07:08 -0400
- Subject: Fwd: [Bug general/3014] New: TestRunner hang at testTaskForkedObserver, after some ERRORs and FAILs
----- Forwarded message from sourceware-bugzilla@sourceware.org -----
Date: 9 Aug 2006 03:04:51 -0000
From: woodzltc at cn dot ibm dot com <sourceware-bugzilla@sourceware.org>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug general/3014] New: TestRunner hang at
testTaskForkedObserver, after some ERRORs and FAILs
To: woodzltc@cn.ibm.com
I am using a script to check out the cvs, build frysk and run the testsuite.
One hour after I started the script, I see it hang at testTaskForkedObserver:
Here is the output:
===================
Running testTaskForkedObserver(frysk.proc.TestTaskForkedObserver)
...execvp: Too
many open files
Error upon logging: OPEN_FAILURE
java.io.FileNotFoundException:
/home/woodzltc/.frysk/logs/frysk_core_event.log.2
(Too many open files)
at gnu.java.nio.channels.FileChannelImpl.open(libgcj.so.7)
at gnu.java.nio.channels.FileChannelImpl.<init>(libgcj.so.7)
at java.io.FileOutputStream.<init>(libgcj.so.7)
at java.util.logging.FileHandler.createFileStream(libgcj.so.7)
at java.util.logging.FileHandler.rotate(libgcj.so.7)
at java.util.logging.FileHandler.publish(libgcj.so.7)
at java.util.logging.Logger.log(libgcj.so.7)
at java.util.logging.Logger.logImpl(libgcj.so.7)
at java.util.logging.Logger.logp(libgcj.so.7)
at java.util.logging.Logger.logp(libgcj.so.7)
at java.util.logging.Logger.log(libgcj.so.7)
at frysk.event.EventLoop.runPolling(TestRunner)
at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
at frysk.proc.TestLib.assertRunUntilStop(TestRunner)
at frysk.proc.TestLib$AckHandler.assertAwait(TestRunner)
at frysk.proc.TestLib$AckHandler.await(TestRunner)
at frysk.proc.TestLib$Child.<init>(TestRunner)
at frysk.proc.TestLib$AckProcess.<init>(TestRunner)
at frysk.proc.TestLib$AckProcess.<init>(TestRunner)
at frysk.proc.TestLib$DetachedAckProcess.<init>(TestRunner)
at frysk.proc.TestLib$AttachedDaemonProcess.<init>(TestRunner)
at frysk.proc.TestTaskForkedObserver.testTaskForkedObserver(TestRunner)
at java.lang.reflect.Method.invoke(libgcj.so.7)
at junit.framework.TestCase.runTest(TestRunner)
at junit.framework.TestCase.runBare(TestRunner)
at junit.framework.TestResult$1.protect(TestRunner)
at junit.framework.TestResult.runProtected(TestRunner)
at junit.framework.TestResult.run(TestRunner)
at junit.framework.TestCase.run(TestRunner)
at junit.framework.TestSuite.runTest(TestRunner)
at junit.framework.TestSuite.run(TestRunner)
at junit.framework.TestSuite.runTest(TestRunner)
at junit.framework.TestSuite.run(TestRunner)
at junit.textui.TestRunner.doRun(TestRunner)
at junit.textui.TestRunner.doRun(TestRunner)
at frysk.junit.Runner.<init>(TestRunner)
at TestRunner.main(TestRunner)
When I look back, I found quite a lot of FAILs, with a similar message:
junit.framework.AssertionFailedError: event loop run explictly stopped
(startChild (Sig_USR1))
These fails start with an ERROR report at testDoCloneAttached:
java.lang.RuntimeException:
{frysk.proc.LinuxTask@e1f900,pid=8463,tid=8463,state=StartMainTask.wantToAttach}
in state "StartMainTask.wantToAttach" did not handle handleRemoval
Before testDoCloneAttached, there are 51 PASSes.
Additional information:
1. I talked this with Phil on IRC, he confirm similar errors.
2. I am running on FC5. I ever run the same testsuite against the cvs code I
checked out at 08-05. no errors found, 100% pass for 137 tests in frysk-core
--
Summary: TestRunner hang at testTaskForkedObserver, after some
ERRORs and FAILs
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: cagney at redhat dot com
ReportedBy: woodzltc at cn dot ibm dot com
CC: pmuldoon at redhat dot com,qiyaoltc at cn dot ibm dot
com,zhengyzy at cn dot ibm dot com
GCC build triplet: i386-redhat-linux
GCC host triplet: i386-redhat-linux
GCC target triplet: i386-redhat-linux
http://sourceware.org/bugzilla/show_bug.cgi?id=3014
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
----- End forwarded message -----
Regards
- Wu Zhou