Bill,
On 3/29/07, William Surowiec <[EMAIL PROTECTED]> wrote:
Well, at least it does to me :) and I am not sure what to make of it.
There are two "unusual" situations I encounter. First, testing issues
SEVERE messages, with Java exceptions, yet the test summary appears
fine.
This is actually expected. Some of our unit tests are testing error
conditions which cause the framework to log SEVERE messages. In your
case the error message is "Test Error" which tells me this is expected
(also the test case that's running has "ErrorTest" in the name).
The second problem is eventually one test seems to go to sleep and
never wakes up - ergo I cannot complete the build.
<snip/>
That's certainly a problem. There may be some race condition (that
particular testcase is multithreaded) that you see but we don't due to
different hardware characteristics or whatnot.
For now, to get the build to complete you can pass the parameter
-Dmaven.test.skip=true when you call "mvn install", which will make it
skip the unit tests entirely.
When I get a chance I can eyeball that test case to see if I can think
of what race condition might be there (hopefully it's in the test
case, not the framework - we've seen that in a few other test cases
before).
Any other debug support you could provide would be great, for example
if you can find out what line of the test is hung at.
-Adam
