Bug 1979 - Fault Tolerance tests not run for scoreboard results.
Summary: Fault Tolerance tests not run for scoreboard results.
Status: ASSIGNED
Alias: None
Product: TAO
Classification: Unclassified
Component: Test (show other bugs)
Version: 1.4.2
Hardware: x86 NetBSD
: P3 normal
Assignee: J.T. Conklin
URL:
: 3098 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-11-11 21:36 CST by J.T. Conklin
Modified: 2007-11-12 03:43 CST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description J.T. Conklin 2004-11-11 21:36:48 CST 
The test code in orbsbvcs/tests/FT_App and orbsvcs/tests/FaultTolerance is not 
executed as part of the scoreboard autobuilds.  This increases the danger of 
changes inadvertantly breaking things without anyone noticing.
Comment 1 Nanbor Wang 2004-11-11 21:53:57 CST 
JT could you please turn on the FaultTolerance tests in the daily builds? My
hands are full and I may not be able to get to this now..

Thanks
Comment 2 J.T. Conklin 2004-11-24 20:56:24 CST 
I've written run_test.pl scripts for orbsvcs/test/FaultTolerance/*.  Since there
seem to be a lot of tests that exist but are not part of the scoreboard results,
I've sent a note to Bala asking what the criteria is before I go ahead and add
them to tao_other_tests.lst.
Comment 3 J.T. Conklin 2004-12-08 12:31:54 CST 
The FaultTolerance tests are now enabled.

I'm assigning this to myself and keeping it open a little longer in order to
investigate getting the FT_App tests running as well.
Comment 4 J.T. Conklin 2004-12-23 13:14:00 CST 
accept bug...
Comment 5 Johnny Willemsen 2005-03-08 06:43:00 CST 
It seems the test 
TAO/orbsvcs/tests/FaultTolerance/GroupRef_Manipulation/run_test.pl fails in all 
our builds. Any idea why?
Comment 6 Johnny Willemsen 2007-11-12 03:42:48 CST 
the FT tests doesn't seem to be in tao_other_tests.lst.
Comment 7 Johnny Willemsen 2007-11-12 03:43:11 CST 
*** Bug 3098 has been marked as a duplicate of this bug. ***