Patrick Hunt commented on ZOOKEEPER-618:

you know, I must have looked at the wrong "consoletext" file (they are all 
named the same by default).

Regardless - in this case there is no report of why the build failed. Looking 
at the console again, I see that it
failed due to some problem during cppunit. We've seen similar though for other 
things like svn checkout failure,
and random build issues like running clover w/o the right libs, etc...

It wold be great at least if the hudson page could indicate that this failed 
due to cppunit failure.

> hudson not reporting failures correctly
> ---------------------------------------
>                 Key: ZOOKEEPER-618
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-618
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: tests
>    Affects Versions: 3.3.0
>            Reporter: Patrick Hunt
>            Assignee: Giridharan Kesavan
>            Priority: Critical
> See
> http://hudson.zones.apache.org/hudson/view/ZooKeeper/job/ZooKeeper-trunk/612/
> this test failed however there is no indication in the hudson page why it 
> failed.
> Looking at the raw console output I see
>     [junit] Running org.apache.zookeeper.test.QuorumTest
>     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
>     [junit] Test org.apache.zookeeper.test.QuorumTest FAILED (timeout)
> So it seems there is an error in hudson reporting.
> Giri can you look into this?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to