testLinuxCoreFileStackTrace(frysk.proc.dead.TestLinuxCore)junit.framework.ComparisonFailure: Compare stack traces expected:<...c40379 in __GI___sigsuspend () #2 0x080492de in server () #3 0x08049d73 in main () #4 0x00c2d4e4 in __libc_start_main () #5 0x08048d41 in _start ()...> but was:<...000000 in [unknown]...> at frysk.proc.dead.TestLinuxCore.testLinuxCoreFileStackTrace(TestRunner) at frysk.junit.Runner.runCases(TestRunner) at frysk.junit.Runner.runArchCases(TestRunner) at frysk.junit.Runner.runTestCases(TestRunner) at TestRunner.main(TestRunner) this is likely caused by a truncated executable path
Test passes for me on x8664 f7 $ ./TestRunner frysk.proc.dead.TestLinuxCore.testLinuxCoreFileStackTrace Running testLinuxCoreFileStackTrace(frysk.proc.dead.TestLinuxCore) ...PASS Time: 0.125 OK (1 test)
fails intermittently
I cannot get this to fail locally. The best thing to do here would be to attach a tar.gz file of both a failing and passing corefile, and compare the differences. The [unknown] in the first frame normally means it got lost early on, which normally means no executable available.
1) testLinuxCoreFileStackTrace(frysk.proc.dead.TestLinuxCore)junit.framework.ComparisonFailure: Compare stack traces expected:<...30afa in __GI___sigsuspend () #1 0x0000000000401755 in server () #2 0x0000000000402162 in main () #3 0x0000003a8101dab4 in __libc_start_main () #4...> but was:<...cdca9 in syscall () #1 0x0000000000401242 in tkill () #2 0x000000000040144e in notify_manager () #3 0x0000000000401667 in server () #4 0x0000000000402162 in main () #5 0x0000003a8101dab4 in __libc_start_main () #6...>
The branch, master has been updated via efc98011cc2d005c62da7050c720e037a9c22944 (commit) from adb971cd44b8398b4f64cecb699ff2c3be8620aa (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit efc98011cc2d005c62da7050c720e037a9c22944 Author: Phil Muldoon <pmuldoon@redhat.com> Date: Thu Nov 15 15:29:59 2007 +0000 Use DaemonBlockedAtSignal in test. 2007-11-15 pmuldoon <pmuldoon@redhat.com> * TestLinuxCore.java (testLinuxCoreFileStackTrace): Use DaemonBlockedAtSignal. Create live map first, then core. -----------------------------------------------------------------------