My take is that those three test aborts should have failed the entire Ant process at the point where the controls tests failed.
Without that, the tests fail and the build continues, and the Ant process can still end in BUILD SUCCESSFUL even if there were aborts.
Probably good to follow the JUnit / Ant model here -- fail early.
:)
Eddie
Joe Pemberton wrote:
Eddie, I'm not sure I follow you. I see the three aborts in the TCH run, and I see a BUILD FAILED at the end of the run. Also, the CC run itself failed.
-Joe
-----Original Message-----
From: Eddie O'Neil Sent: Wednesday, March 16, 2005 10:45 AM
To: Beehive Developers
Subject: Re: Beehive Check-in Test (Linux) Failed
A second-order problem is that there are three tests in the TCH test suite that were aborted (and even stack traced), but these didn't fail the controls test suite. Look at this link and scroll down to the TCH output:
http://beehive01.bea.com/downloads/20050316052618/general/build.out
Zach, can you take a look at this? We saw the same thing with some controls test failures last week.
Eddie
Daryl Olander wrote:
So it appears that there is a break in the controls checkin tests that was caused by the same checkin from this morning.
http://svn.apache.org/viewcvs.cgi?rev=157742&view=rev
CC was broken at 5:26 this morning. There were two sets of failures, the WSM Drts failed in addition the controls check in test failed
http://beehive01.bea.com/downloads/20050316052618/controls/tch.cout
There is only a single checkin here.
On Wed, 16 Mar 2005 10:33:09 -0800 (PST), [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
View results here ->
http://beehive01.bea.com/cruisecontrol/buildresults?log=log2005031610210 0
