activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3842) test units: disk space requirement excessive/not checked transparently enough
Date Fri, 18 May 2012 20:01:37 GMT

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

Timothy Bish commented on AMQ-3842:
-----------------------------------

The error messages simply point out that the configuration could lead to issues.  The tests
themselves don't really need 50gig.  Why its hanging probably doesn't have any relation to
the error especially for the test case shown.  You could easily validate this by changing
the test to reduce the configured min space requirement and see if it still hangs.  
                
> test units: disk space requirement excessive/not checked transparently enough
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-3842
>                 URL: https://issues.apache.org/jira/browse/AMQ-3842
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Test Cases
>    Affects Versions: 5.6.0
>         Environment: any
>            Reporter: Mark
>            Priority: Trivial
>
> persistent DB requires at least 50.000 MB free temp. disk space at broker startup during
tests. If there is less available, an error is logged to active-mq.log, but the tests just
hang.
> 1.) Do we really need 50 GB free disk space for the tests?
> 2.) The error should trigger an immediate test failure.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message