I have just started to get into the ActiveMQ code and I like it. I also like the unit tests. However, the past three days or so they have refused to cooperate. To summarize:
1) They fail on Windows 7, period. If someone can run "mvn clean package" successfully from a Windows 7 command prompt please let me know. At least one test fails because Windows won't delete a file when it is open (and it is). Others fail with what I think are similar problems - I haven't had time to analyze them in depth. 2) They fail on old hardware. My main development environment runs Windows, so I tried with an old Linux box. No luck. With --fail-never most tests completed, but some failed and it took an entire day. I don't see that as a big problem, it is hard to write a load test that scales down to outdated hardware. 3) They fail on CentOS 7 in VirtualBox. Clean minimal install with git and mvn, 4 CPUs and 4 G RAM. Might be an SELinux thing, I haven't found out yet. This raises two questions. The first is how I can unit test effectively before pushing to Jenkins? Is there a known good setup that works or a Maven profile that needs to be activated that I have missed or something? The second question is more important - how do we know that ActiveMQ works on Windows when several unit tests always fail on Windows and (as far as I can see) that has been true for quite some time? -Erik -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-Running-unit-tests-successfully-locally-tp4701962.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
