[ 
https://issues.apache.org/jira/browse/CASSANDRA-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969108#action_12969108
 ] 

Jonathan Ellis commented on CASSANDRA-1834:
-------------------------------------------

usually when i've seen "vm exited abnormally" there is something in the log or 
on stdout, can we get the subprocess stdout from hudson?

> hudson test failure: "Forked Java VM exited abnormally."
> --------------------------------------------------------
>
>                 Key: CASSANDRA-1834
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1834
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Eric Evans
>
> https://hudson.apache.org/hudson/view/A-F/view/Cassandra/job/Cassandra-0.7/56/
> {noformat}
>     [junit] Testsuite: 
> org.apache.cassandra.service.EmbeddedCassandraServiceTest
>     [junit] Testsuite: 
> org.apache.cassandra.service.EmbeddedCassandraServiceTest
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
>     [junit] 
>     [junit] Testcase: 
> org.apache.cassandra.service.EmbeddedCassandraServiceTest:BeforeFirstTest:    
>   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 exit.
>     [junit] 
>     [junit] 
>     [junit] Test org.apache.cassandra.service.EmbeddedCassandraServiceTest 
> FAILED (crashed)
> {noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to