[ 
https://issues.apache.org/jira/browse/LUCENE-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621136#comment-13621136
 ] 

Dawid Weiss commented on LUCENE-4901:
-------------------------------------

IBM definitely dumps a *lot* of stuff when it crashes. But isn't build/ cwd 
cleaned up on each build? I run such tests for randomizedtesting so if needed I 
can crash anything (J9, jrockit, hotspot). The way I do it is I link to a small 
snippet of native code (there are binaries for all platforms) which 
dereferences a null pointer. This core-dumps the JVM sort of by-design.

                
> Unit test TestIndexWriterOnJRECrash does not support IBM Java 
> --------------------------------------------------------------
>
>                 Key: LUCENE-4901
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4901
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: general/test
>    Affects Versions: 4.2
>         Environment: Red Hat EL 6.3
> IBM Java 1.6.0
> ANT 1.9.0
>            Reporter: Rodrigo Trujillo
>            Assignee: Dawid Weiss
>            Priority: Minor
>             Fix For: 4.2
>
>         Attachments: test-IBM-java-vendor.patch
>
>
> I successfully compiled Lucene 4.2 with IBM.
> Then ran unit tests with the nightly option set to "true"
> The test case TestIndexWriterOnJRECrash was skipped returning "IBM 
> Corporation JRE not supported":
> [junit4:junit4] Suite: org.apache.lucene.index.TestIndexWriterOnJRECrash
> [junit4:junit4] IGNOR/A 0.28s | TestIndexWriterOnJRECrash.testNRTThreads
> [junit4:junit4]    > Assumption #1: IBM Corporation JRE not supported.
> [junit4:junit4] Completed in 0.68s, 1 test, 1 skipped

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]

Reply via email to