activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-3842) test units should run discovery mechanism via loopback device
Date Fri, 18 May 2012 21:11:12 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark updated AMQ-3842:
----------------------

     Regression: Unit Test Broken
    Description: Many test units are failing on boxes with NAT firewalls enabled, although
discovery via loopback device would (IMHO) be sufficient for test units.  (was: 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.)
    Environment: NAT FW  (was: any)
         Labels: discovery  (was: )
        Summary: test units should run discovery mechanism via loopback device  (was: test
units: disk space requirement excessive/not checked transparently enough)
    
> test units should run discovery mechanism via loopback device
> -------------------------------------------------------------
>
>                 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: NAT FW
>            Reporter: Mark
>            Priority: Trivial
>              Labels: discovery
>
> Many test units are failing on boxes with NAT firewalls enabled, although discovery via
loopback device would (IMHO) be sufficient for test units.

--
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