It has happened before as well. Everything runs nice on the CI machine
for a while, and everything runs perfectly on my local machine, but
for some reason the Struts2PortletTest fails now and then on the CI
machine. Like java.io.FileNotFoundException: no such file: /tmp/
Nils,
I think the problem is that the tests in Struts2PortletTest can't be
run in parallel.
If you check out two test histories in the Java6 project VS MAIN:
http://opensource.bamboo.atlassian.com/browse/STRUTS-MAINJ6/test/
org.apache.struts2.portlet.test.Struts2PortletTest:testFormExample
Thanks for the input, Mark!
I have tried setting up the tests locally with the maven target
folder as the web-app temp directory instead. I assume this will be
independent for the two builds, so it should work. I'll commit the
fixes and see what happens.
Nils-H
On Nov 26, 2007 1:18 AM, Mark
I checked in a very minor change for WW-2328 and now the
Struts2PortletTest is failing in both the java5 and java6 bamboo
builds--but with different exceptions. I have a clean checkout of
struts2 and everything builds fine locally with a mvn -Pall build. So
is this a case of gremlins in the
