[ http://issues.apache.org/jira/browse/BEEHIVE-448?page=history ]
Steve Tocco updated BEEHIVE-448:
--------------------------------
Fix Version: V1
moving to v1 (if not needed for ship, please move to Fix For = TBD)
> controls TCH test infrastructure doesn't fail the build when the tests fail
> ---------------------------------------------------------------------------
>
> Key: BEEHIVE-448
> URL: http://issues.apache.org/jira/browse/BEEHIVE-448
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: V1Beta
> Reporter: Eddie O'Neil
> Assignee: Zach Smith
> Priority: Critical
> Fix For: V1
>
> When the controls DRTs run and tests are aborted, the test run does not fail.
> This produces a false positive success on the run. An example can be seen
> here:
> http://beehive01.bea.com/downloads/20050316052618/general/build.out
> Scroll down to look at the output of TCH and see three aborts.
> These aborts stack traced here:
> http://beehive01.bea.com/downloads/20050316052618/controls/tch.cout
> Probably a good idea to fail the build on DRT runs that don't pass so that
> failures are obvious.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
