I notice that there is a typo in the address you have; the correct URL
is below.  I don't know if it is open in the firewall or not; it does
resolve externally (where beahive01.bea.com wouldn't).

http://beehive01.bea.com:9090/cruisecontrol/buildresults

- jeremiah

-----Original Message-----
From: Bryan Che [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 01, 2005 3:42 PM
To: James Song
Cc: Beehive Developers
Subject: Re: expected controls detailed.tests output?

OK, that's good to know.  It would be helpful if there was some place to

get canonical test results, including expected failures.  There was an 
e-mail a while back pointing at 
http://beahive01.bea.com:9090/cruisecontrol/buildresults, but that 
machine isn't externally viewable.

Thanks,

Bryan

James Song wrote:
> Bryan:
> 
> Controls detailed.tests do not pass 100%, this is by design
> temporarily.Only checkin.tests pass 100% at this moment.
> 
> -James
> -----Original Message-----
> From: Bryan Che [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, February 01, 2005 12:42 PM
> To: Beehive Developers
> Subject: expected controls detailed.tests output?
> 
> Hi, I just tried running the detailed.tests target in 
> controls/test/build.xml on Linux and got the following results:
> 
>        [tch] TOTALS
>        [tch] -------
>        [tch] TOTAL TESTS:          54
>        [tch] SUCCESSES:            37  (68.52%)
>        [tch] FAILURES:             13  (24.07%)
>        [tch] ABORTS:               4  (7.41%)
>        [tch] SKIPS:                0  (0.0%)
>        [tch] VALIDATION SKIPS:     0  (0.0%)
>        [tch] TIMEOUTS:             0  (0.0%)
> 
>        [tch] INVALIDATIONS:        0
>        [tch] SCRATCHES:            0
>        [tch] ABANDONS:             0
> 
> Are other people getting the same failures/aborts?  The controls 
> drt/checkin tests run with no problems (It's also a bit strange that
the
> 
> checkin/drt tests run more tests than the detailed tests).
> 
> I'm asking because I have local changes to my build/test system and am

> looking for a sanity check.  From the errors, it doesn't look like
I've 
> done anything to make the tests fail, but I want to be sure.
> 
> I'm at SVN revision 149432.
> 
> Thanks,
> 
> Bryan
> 

Reply via email to