Bug 3066 - frysk-core testsuite failures on x86_64
Summary: frysk-core testsuite failures on x86_64
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on: 3099
Blocks: 2127
  Show dependency treegraph
 
Reported: 2006-08-15 18:05 UTC by Stepan Kasal
Modified: 2006-11-28 16:51 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build: x86_64
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stepan Kasal 2006-08-15 18:05:14 UTC
There were 4 failures:
1)
testDetachClone(frysk.proc.TestTaskObserverDetach)junit.framework.AssertionFailedError:
pending signal Sig_USR1
   at frysk.proc.TestLib.tearDown(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)
2)
testSyscallLoop(frysk.proc.TestTaskSyscallObserver)junit.framework.AssertionFailedError:
inSyscall (last call doesn't exit)
   at frysk.proc.TestTaskSyscallObserver.testSyscallLoop(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)
3)
testSyscalls(frysk.proc.TestTaskSyscallObserver)junit.framework.AssertionFailedError:
syscall events
   at frysk.proc.TestTaskSyscallObserver.testSyscalls(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)
4)
testSyscallOpen(frysk.proc.TestTaskSyscallObserver)junit.framework.AssertionFailedError:
in syscall
   at frysk.proc.TestTaskSyscallObserver.testSyscallOpen(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)

I'm going to disable them with brokenXXX in the CVS.
Comment 1 Stepan Kasal 2006-08-18 18:55:03 UTC
No, they should not be disabled by brokenXXX, because that would exclude them
from junit runs, too.
Comment 2 Stepan Kasal 2006-08-18 19:08:46 UTC
testDetachClone is fixed now, the other three remain.
Comment 3 Stepan Kasal 2006-08-21 15:45:12 UTC
The build system uses:
Linux 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 i686 i686 i386 GNU/Linux

If the problems can be blamed on this kernel, then the right solution is to
switch off the checks (at the build time only).
Comment 4 Mark Wielaard 2006-08-21 16:38:19 UTC
./TestRunner frysk.proc.TestTaskObserverDetach and 
./TestRunner frysk.proc.TestTaskObserverDetach passes for me on both:
2.6.17-1.2174_FC5 x86_64 GNU/Linux
2.6.17-1.2573.fc6 i686 i386 GNU/Linux