This is the mail archive of the frysk@sources.redhat.com mailing list for the frysk project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Disable testThreadedBacktrace on ! ia32


Hi, Mark,
testThreadedBacktrace fails on my box(x86 rawhide, but FC5 kernel).
My gcc version is 4.1.1 20060917 (Red Hat 4.1.1-23).

Here are two problems,

a) function name is "clone" instead of "__clone"
I add some "System.err.println" in this case, and here is the output,

[qiyao@GreenHouse frysk-core]$ ./TestRunner
frysk.rt.tests.TestStackBacktraceRunning
testBacktrace(frysk.rt.tests.TestStackBacktrace) ...PASS
Running testThreadedBacktrace(frysk.rt.tests.TestStackBacktrace)
...__libc_start_main
clone
FAIL
  junit.framework.ComparisonFailure: expected:<__...> but was:<...>

Time: 0.403
There was 1 failure:
1)
testThreadedBacktrace(frysk.rt.tests.TestStackBacktrace)junit.framework.ComparisonFailure:
expected:<__...> but was:<...>
   at frysk.rt.tests.TestStackBacktrace.frameAssertions(TestRunner)
   at
frysk.rt.tests.TestStackBacktrace.testThreadedBacktrace(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)

FAILURES!!!
Tests run: 2,  Failures: 1,  Errors: 0

It seems that output is "clone" instead of "__clone".  Does the
function name vary from different versions of library?  I do not know
what happened on your box when run this case, so I do not change
"__clone" to "clone" in this case.


b) Compilation flags to test case affect the result.
If we compile funit-rt-threader without "-g", the result is like this,
Time: 0.341
There was 1 error:
1)
testThreadedBacktrace(frysk.rt.tests.TestStackBacktrace)java.lang.NullPointerException
   at frysk.rt.tests.TestStackBacktrace.frameAssertions(TestRunner)
   at
frysk.rt.tests.TestStackBacktrace.testThreadedBacktrace(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)
There was 1 failure:
1)
testBacktrace(frysk.rt.tests.TestStackBacktrace)junit.framework.AssertionFailedError:
expected:<61> but was:<62>
   at frysk.rt.tests.TestStackBacktrace.testBacktrace(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)

FAILURES!!!
Tests run: 2,  Failures: 1,  Errors: 1

Compile funit-rt-threder with "-g", the result is like this,
[qiyao@GreenHouse frysk-core]$ ./TestRunner
frysk.rt.tests.TestStackBacktrace
Running testBacktrace(frysk.rt.tests.TestStackBacktrace) ...FAIL
  junit.framework.AssertionFailedError: expected:<61> but was:<62>
Running testThreadedBacktrace(frysk.rt.tests.TestStackBacktrace)
...FAIL
  junit.framework.AssertionFailedError: expected:<71> but was:<72>

Time: 0.39
There were 2 failures:
1)
testBacktrace(frysk.rt.tests.TestStackBacktrace)junit.framework.AssertionFailedError:
expected:<61> but was:<62>
   at frysk.rt.tests.TestStackBacktrace.testBacktrace(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)
2)
testThreadedBacktrace(frysk.rt.tests.TestStackBacktrace)junit.framework.AssertionFailedError:
expected:<71> but was:<72>
   at frysk.rt.tests.TestStackBacktrace.frameAssertions(TestRunner)
   at
frysk.rt.tests.TestStackBacktrace.testThreadedBacktrace(TestRunner)
   at frysk.junit.Runner.<init>(TestRunner)
   at TestRunner.main(TestRunner)

FAILURES!!!
Tests run: 2,  Failures: 2,  Errors: 0

-- 
Yao Qi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]