[
https://issues.apache.org/jira/browse/LUCENE-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103026#comment-13103026
]
Dawid Weiss commented on LUCENE-3429:
-------------------------------------
Errr... I get a repetitive vm crash after applying the above patch.
{noformat}
[junit] #
[junit] # A fatal error has been detected by the Java Runtime Environment:
[junit] #
[junit] # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at
pc=0x000000006dae29a5, pid=4040, tid=5104
[junit] #
[junit] # JRE version: 6.0_26-b03
[junit] # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode
windows-amd64 compressed oops)
[junit] # Problematic frame:
[junit] # V [jvm.dll+0x2529a5]
[junit] #
[junit] # An error report file with more information is saved as:
[junit] #
d:\work\apache.org\lucene.git\lucene\build\test\7\hs_err_pid4040.log
[junit] #
[junit] # If you would like to submit a bug report, please visit:
[junit] # http://java.sun.com/webapps/bugreport/crash.jsp
[junit] #
[junit] Testsuite: org.Batch-With-Multiple-Tests
[junit] Testcase: org.Batch-With-Multiple-Tests:testFlushExceptions:
Caused an ERROR
[junit] Forked Java VM exited abnormally. Please note the time in the
report does not reflect the time until the VM exit.
[junit] junit.framework.AssertionFailedError: Forked Java VM exited
abnormally. Please note the time in the report does not reflect the time until
the VM ex
it.
[junit] at java.lang.Thread.run(Thread.java:662)
[junit]
{noformat}
Is this something new or known? I'm on win7, 64-bit - can anybody check on
other machines?
> improve build system when tests hang
> ------------------------------------
>
> Key: LUCENE-3429
> URL: https://issues.apache.org/jira/browse/LUCENE-3429
> Project: Lucene - Java
> Issue Type: Test
> Reporter: Robert Muir
> Fix For: 3.5, 4.0
>
> Attachments: LUCENE-3429.patch, LUCENE-3429.patch
>
>
> Currently, if tests hang in hudson it can go hung for days until we manually
> kill it.
> The problem is that when a hang happens its probably serious, what we want to
> do (I think), is:
> # time out the build.
> # ensure we have enough debugging information to hopefully fix any hang.
> So I think the ideal solution would be:
> # add a sysprop "-D" that LuceneTestCase respects, it could default to no
> timeout at all (some value like zero).
> # when a timeout is set, LuceneTestCase spawns an additional timer thread for
> the test class? method?
> # if the timeout is exceeded, LuceneTestCase dumps all thread/stack
> information, random seed information to hopefully reproduce the hang, and
> fails the test.
> # nightly builds would pass some reasonable -D for each test.
> separately, I think we should have an "ant-level" timeout for the whole
> build, in case it goes completely crazy (e.g. jvm completely hangs or
> something else), just as an additional safety.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
