Bug 3530 - testThreadedBacktrace(frysk.rt.tests.TestStackBacktrace)junit.framework.ComparisonFailure: expected:<signal_parent> but was:<bak>
Summary: testThreadedBacktrace(frysk.rt.tests.TestStackBacktrace)junit.framework.Compa...
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Mike Cvet
URL:
Keywords:
Depends on:
Blocks: 2935
  Show dependency tree / graph
 
Reported: 2006-11-16 20:23 UTC by Nurdin Premji
Modified: 2006-12-27 15:51 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nurdin Premji 2006-11-16 20:23:36 UTC 
Intermittent failure:
 
testThreadedBacktrace(frysk.rt.tests.TestStackBacktrace)junit.framework.ComparisonFailure:
expected:<signal_parent> but was:<bak>
    at frysk.rt.tests.TestStackBacktrace.frameAssertions(TestRunner)
    at frysk.rt.tests.TestStackBacktrace.testThreadedBacktrace(TestRunner)
    at frysk.junit.Runner.runCases(TestRunner)
    at frysk.junit.Runner.runArchCases(TestRunner)
    at frysk.junit.Runner.runTestCases(TestRunner)
    at TestRunner.main(TestRunner)
Comment 1 Mike Cvet 2006-11-16 20:25:51 UTC 
Test assumes that main task tid is always < the other threads
Comment 2 Mike Cvet 2006-12-27 15:51:08 UTC 
2006-12-27  Mike Cvet  <mcvet@redhat.com>

	* TestStackBacktrace.java (frameAssertions): Now determines the
	identity of stack frames by innermost frame function name, rather than
	relative TID. Fixes #3530.