You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Beliaev (JIRA)" <ji...@apache.org> on 2007/01/31 13:11:05 UTC
[jira] Commented: (HARMONY-1845) [drlvm][finalizers] Thread Manager
internal error 720006
[ https://issues.apache.org/jira/browse/HARMONY-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469007 ]
Vladimir Beliaev commented on HARMONY-1845:
-------------------------------------------
The issue is not reproducible any more.
I can't claim the kernel tests running is just fine (e.g. java.lang.RuntimeAdditionalTest43 halts with exception) , still this particular test - java.lang.RuntimeAdditionalTest4 - passes on mentioned configuration (win_ia32_msvc_debug) with int/jet/opt.
Please get JIRA set to resolved state.
I believe, including RuntimeAdditionalTest4 back to kernel tests run is another task - now all of the RuntimeAdditionalTest* are excluded.
BTW...
It's really a fun to find a way to run single Kernel test... In short - no inherent-to-build way, no documentation. Finally I've just:
1. entered working_vm/vm/tests/kernel/.
2. found all java sources
3. put their names to 3 exclude lists:
working_vm/build/make/excludes/exclude.drlvm_kernel.windows.x86.*
4. then I've run test (the target was found in build.xml files):
cd working_vm/build
./build.bat kernel.test
The stripped log are (I've removed too long excluded list, etc):
-run-kernel-test-batch:
[echo] ==================================
[echo] Run kernel tests using jitrino.JET
[echo] ==================================
[junit] Running java.lang.RuntimeAdditionalTest4
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 10.967 sec
-run-kernel-test-batch:
[echo] ==================================
[echo] Run kernel tests using jitrino.OPT
[echo] ==================================
[junit] Running java.lang.RuntimeAdditionalTest4
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 21.853 sec
-run-kernel-test-batch:
[echo] ==================================
[echo] Run kernel tests using interpreter
[echo] ==================================
[junit] Running java.lang.RuntimeAdditionalTest4
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 27.189 sec
Thanks
Vladimir Beliaev
> [drlvm][finalizers] Thread Manager internal error 720006
> --------------------------------------------------------
>
> Key: HARMONY-1845
> URL: https://issues.apache.org/jira/browse/HARMONY-1845
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: win_ia32_msvc_debug
> Reporter: Serguei Zapreyev
>
> If the 1834 patch is used to extend the kernel tests then the renewed
> java.lang.RuntimeAdditionalTest4 fails often and often (at least for me) for jitrino.jet and
> jitrino.opt modes as follows:
> <<<...>>>
> [echo]
> [echo] ==================================
> [echo] Run kernel tests using jitrino.jet
> [echo] ==================================
> [echo]
> [mkdir] Created dir: C:\IJE\G577\trunk\working_vm\build\win_ia32_msvc_debug\
> semis\kernel.tests\reports\jitrino.jet
> [echo] RUNNING : java.lang.RuntimeAdditionalTest4
> [junit] FinalizerThread: FinalizerThread terminated by java.lang.InternalErr
> or: Thread Manager internal error 720006
> [junit] Uncaught exception in FinalizerThread:
> [junit] java.lang.RuntimeException: FinalizerThread interrupted
> [junit] at java.lang.FinalizerThread.run(Unknown Source)
> [junit] Caused by: java.lang.InternalError: Thread Manager internal error 72
> 0006
> [junit] at java.lang.Object.notify(Unknown Source)
> [junit] ... 1 more
> [junit] Test java.lang.RuntimeAdditionalTest4 FAILED (timeout)
> [junitreport] Transform time: 741ms
> [junitreport] Transform time: 250ms
> [echo] ==============================================
> [echo] Kernel tests FAILED using jitrino.jet. Please find the detailed resu
> lts here:
> [echo] C:\IJE\G577\trunk\working_vm\build\win_ia32_msvc_debug\semis\kernel.
> tests\reports\jitrino.jet\html\index.html
> [echo] ==============================================
> <<<...>>>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.