Re: [Axis2] 1.5 branch build broken

[Andreas Veithen <an...@gmail.com>]

Dennis,

Jarek recently modified the surefire plugin configuration (in the
trunk and the 1.5) to redirect the test output to files. Anyway, the
best way to identify the failed test cases is to look at the surefire
reports (in target/surefire-reports). I tested the build on Linux with
Sun 1.6.0_10, but I don't see any test failure. Can you post the
surefire reports for the failing tests?

Andreas

On Mon, Jun 28, 2010 at 04:54, Dennis Sosnoski <dm...@sosnoski.com> wrote:
> Andreas Veithen wrote:
>>
>> Dennis,
>>
>> I don't know any project that systematically tests its builds with all
>> possible combinations of Maven version, Java version, Maven settings
>> (e.g. maven.test.skip), platform (Windows, Linux, Mac OS X) and
>> preconditions (local repository empty or not). We have Hudson jobs and
>> these builds work fine. If people encounter problems in a specific
>> environment or when running with non standard Maven settings, we
>> expect them to report the issue and provide enough information to
>> track down the issue.
>>
>
> I was running "mvn clean install" from a clean checkout of the branch, as I
> said in the original email about the missing Axiom jars. I'm running on
> Mandriva Linux 2009.1, using the Sun 1.6.0_10 JVM and Maven 2.0.11.
>
>> For the jaxws-integration test issues, you simply complain but don't
>> provide any relevant info about the issue. I'm tempted to say: as
>> usual...  :-(
>>
>
> The big problem here is that the jaxws-integration test spews out dozens of
> stack traces and other verbose console output as part of the normal
> execution, so it's not at all clear to me what specific problem is causing
> the build to fail. The final output shows only one of the actual failed
> tests, which is:
>
> Caused by:
> org.apache.axis2.jaxws.sample.asyncdoclit.server.ThrowExceptionFault:
> message
>
>       at
> org.apache.axis2.jaxws.sample.asyncdoclit.server.DocLitWrappedPortImpl.throwException(DocLitWrappedPortImpl.java:229)
>
>       ... 17 more
>  AsyncClient.waitBlocking Exit, 29sec remaining
>     [SimpleHTTPServer] Stop called
>       Tests run: 10, Failures: 2, Errors: 0, Skipped: 0, Time elapsed:
> 16.381 sec <<< FAILURE!
>
> [SimpleHTTPServer] Stop called
>   Running
> org.apache.axis2.jaxws.xmlhttp.clientTests.dispatch.string.DispatchXPayloadStringTests
>
> [SimpleHTTPServer] Stop called
>   Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.024 sec
>      Running org.apache.axis2.jaxws.security.BasicAuthSecurityTests
> [SimpleHTTPServer] Stop called
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.172 sec
>
> Results :
>
> Failed tests:
>
> Tests run: 318, Failures: 7, Errors: 0, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
>
>> The jaxws-integration test issue has existed for quite some time in
>> the trunk, but got fixed in a couple of days after it became clear
>> that all the people who were complaining about this were actually
>> trying to build with maven.test.skip=true (but forgot to mention
>> this...).
>>
>
> I'm using "mvn clean install", as I said before. No other settings apply.
>
>  - Dennis
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org