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/
Jetty_0_0_0_0_0_webapp__test__-111m18/​jsp/​org/​apache/​jsp/
WEB_002dINF/​view/​tokenExampleInput_jsp.class". Are there some
special restrictions or anything with the tmp folder that could
explain this failure? I guess I'll exclude the tests from the build
for now, but I would really like to have them running...

Nils-H

On Nov 25, 2007 10:25 AM, Tom Schneider <[EMAIL PROTECTED]> wrote:
> 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 s2 build, or did I really break
> something and just can't reproduce it?
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to