diff options
26 files changed, 90 insertions, 82 deletions
diff --git a/TAO/tests/AMI_Timeouts/README b/TAO/tests/AMI_Timeouts/README index e7759a0d5f7..8e813f48778 100644 --- a/TAO/tests/AMI_Timeouts/README +++ b/TAO/tests/AMI_Timeouts/README @@ -1,4 +1,4 @@ -# $Id$ +$Id$ Description: This is a simple test for AMI callback model in combination with @@ -9,7 +9,7 @@ Use TAO_HAS_CORBA_MESSAGING and TAO_HAS_AMI_CALLBACK to compile TAO. This enables the AMI code in it. -Use -GC on the TAO IDL compiler to generate code for AMI callbacks. +Use -GC on the TAO IDL compiler to generate code for AMI callbacks. Usage: ===== diff --git a/TAO/tests/BiDirectional/README b/TAO/tests/BiDirectional/README index d9e85d7900b..f6d87642d2e 100644 --- a/TAO/tests/BiDirectional/README +++ b/TAO/tests/BiDirectional/README @@ -1,10 +1,10 @@ -# $Id$ +$Id$ This is a test that exercises the birectional GIOP connection implementation in TAO. Start the server like this $ server -o <file.ior> -i <no_iterations> -$ client -k file://<file.ior> -x +$ client -k file://<file.ior> -x The server starts up writing the IOR to the file. The client then starts up, creates its own object and passes the reference to the @@ -16,4 +16,4 @@ connection the server would crash itself. To test the fix for bug 3282, run run_test_bug3282.pl or use the commands $ server -ORBEndpoint iiop://localhost -o <file.ior> -i <no_iterations> -$ client -k file://<file.ior> -x +$ client -k file://<file.ior> -x diff --git a/TAO/tests/Bug_2494_Regression/README b/TAO/tests/Bug_2494_Regression/README index 726419360b1..6909ae1fcec 100644 --- a/TAO/tests/Bug_2494_Regression/README +++ b/TAO/tests/Bug_2494_Regression/README @@ -1,30 +1,30 @@ -# $Id$ +$Id$ Description: This test a modification of MT_Server. In this case the client is also -multi-threaded. The client sends very large strings to the server, which it +multi-threaded. The client sends very large strings to the server, which it echoes back, for the sake of keeping the server busy doing I/O. When the client is abruptly killed, the server should close the connection and continue -running. +running. Expected output: - The server prints out the IOR of the object it serves and the + The server prints out the IOR of the object it serves and the results of server shutdown (aborted or shutdown cleanly). Regression: -Activated as +Activated as <IOR:012a2a2a1600000049444c3a53696d706c655f5365727665723a312e30002a2a0100000000000000740000000101022a130000006f6369313332392e6f63697765622e636f6d002a19842a2a1b00000014010f0052535420c93244520b04000000000001000000010000002a020000000000000008000000012a2a2a004f41540100000018000000012a2a2a0100010001000000010001050901010000000000> ***Client has been killed*** -ACE_ASSERT (32395|3067820976): file Transport.cpp, line 172 assertion +ACE_ASSERT (32395|3067820976): file Transport.cpp, line 172 assertion failed for 'this->head_ == 0'.Aborting... -ERROR: cannot find file -</tao_builds/mitza/1.4a/ACE_wrappers/TAO/tests/Bug_2494_Regression/server_terminated> +ERROR: cannot find file +</tao_builds/mitza/1.4a/ACE_wrappers/TAO/tests/Bug_2494_Regression/server_terminated> -- server has not shut down cleanly. (perl script returns 1) Correct run: -Activated as +Activated as <IOR:012a2a2a1600000049444c3a53696d706c655f5365727665723a312e30002a2a0100000000000000740000000101022a130000006f6369313332392e6f63697765622e636f6d002a34842a2a1b00000014010f0052535488d03244438d04000000000001000000010000002a020000000000000008000000012a2a2a004f41540100000018000000012a2a2a0100010001000000010001050901010000000000> ***Client has been killed*** event loop finished diff --git a/TAO/tests/Bug_2966_Regression/README b/TAO/tests/Bug_2966_Regression/README index 224c81775e4..c326f17ec00 100644 --- a/TAO/tests/Bug_2966_Regression/README +++ b/TAO/tests/Bug_2966_Regression/README @@ -1,5 +1,7 @@ /** +$Id$ + @page DII Test README File The goals of writing this test are: @@ -9,7 +11,7 @@ o Deferred twoway DII (i.e. using Request::send_deferred/Request::get_response) o Deferred twoway DII with polling (i.e. using Request::send_deferred/Request::poll_response) o Oneway DII (i.e. using Request::send_oneway) - + To run the test use the run_test.pl script: $ ./run_test.pl diff --git a/TAO/tests/Bug_3826_Regression/README b/TAO/tests/Bug_3826_Regression/README index 63740e99086..c6206bdd980 100644 --- a/TAO/tests/Bug_3826_Regression/README +++ b/TAO/tests/Bug_3826_Regression/README @@ -1,4 +1,4 @@ -// $Id$ +$Id$ This test checks that if the first ORB is created with -ORBGestalt LOCAL then the settings from this ORB will not become default for the other ORBs @@ -23,5 +23,5 @@ Testing with -ORBSvcConf Initialize ORB instances... After ORB_init... ERROR: '-ORBConnectionCacheMax' is applied globally while it's expected to apply to the first ORB only. -ERROR: <server> failed: +ERROR: <server> failed: ERROR: server returned 255 diff --git a/TAO/tests/Codec/README b/TAO/tests/Codec/README index b6fd0b21114..3e82f102d10 100644 --- a/TAO/tests/Codec/README +++ b/TAO/tests/Codec/README @@ -1,7 +1,7 @@ -# $Id$ +$Id$ This test verifies that CodecFactory and CDR encapsulation Codec -support is working properly. +support is working properly. It does so by encoding a structure into an octet sequence, decoding into a new instance of the structure from the octet sequence, and then diff --git a/TAO/tests/Connection_Timeout/README b/TAO/tests/Connection_Timeout/README index 05a7ee90273..3a5326987e8 100644 --- a/TAO/tests/Connection_Timeout/README +++ b/TAO/tests/Connection_Timeout/README @@ -1,12 +1,14 @@ /** +$Id$ + @page Connection_Timeout Test README File The simplest possible test for the proprietary Connection_Timeouts. This test sets the connection timeouts through a policy. The client tries to connect to an non-existent server. The timeout for the connection is controlled by the value supplied by that -policy. +policy. $ ./run_test.pl diff --git a/TAO/tests/DiffServ/README b/TAO/tests/DiffServ/README index fbbbf2ae943..5c3b5e9d224 100644 --- a/TAO/tests/DiffServ/README +++ b/TAO/tests/DiffServ/README @@ -3,7 +3,7 @@ $Id$ This is a unit test for setting DiffServ Codepoint both in the requests sent and the replies received. -To run (on Unix): +To run (on Unix): ----------------- $ ./server -ORBdebuglevel 1 -p 20000 diff --git a/TAO/tests/Hello/README b/TAO/tests/Hello/README index ee77329decb..dec8197b103 100644 --- a/TAO/tests/Hello/README +++ b/TAO/tests/Hello/README @@ -1,5 +1,7 @@ /** +$Id$ + @page Hello Test README File The simplest possible test for TAO. This is a very simple @@ -26,7 +28,7 @@ anything useful, i.e. chances are that this test will always pass. type codes or Anys. Please refrain from "improving", extending or expanding this -test, if you need to change +test, if you need to change To run the test use the run_test.pl script: diff --git a/TAO/tests/IDL_Inherited_Operation/README b/TAO/tests/IDL_Inherited_Operation/README index 2bde20e4f2a..4e4434a5e6c 100644 --- a/TAO/tests/IDL_Inherited_Operation/README +++ b/TAO/tests/IDL_Inherited_Operation/README @@ -1,33 +1,35 @@ /** +$Id$ + @page IDL Inherited Operation Test README File This test checks that an IDL compiler bug, fixed by - + Fri Mar 20 16:04:58 UTC 2009 Jeff Parsons <j.parsons@vanderbilt.edu> never gets re-introduced. The IDL declarations that caused the original bug are: - + - A base interface, with an operation, is declared inside 2 - nested modules. + nested modules. - The nested modules are closed. - The nested modules are reopened, and forward declaration of - the base interface appears inside. + the base interface appears inside. - The nested modules are closed. - The outer module is reopened, and a derived interface declaration appears inside, using the partially scoped name of the base interface. - + This type of IDL caused the base interface operation to be missing from the operation table in generated code for the derived interface. Client calls to this operation on a derived object would result in a BAD_OPERATION exception. - + The test is here instead of in the IDL_Test directory because the bug can be detected only at runtime, by a remote call. IDL_Test is designed to catch only: - + - Error messages incorrectly caused by legal IDL - Errors from incompilable generated code - Incorrect repository IDs, fetched by a local stub call diff --git a/TAO/tests/IORManipulation/README b/TAO/tests/IORManipulation/README index 10fb424eccc..2aaf48aec27 100644 --- a/TAO/tests/IORManipulation/README +++ b/TAO/tests/IORManipulation/README @@ -1,3 +1,5 @@ +$Id$ + This program test the basic operation of TAO's IORManipulation interface. @@ -10,4 +12,4 @@ Comments: - The various stages of the test are printed out. Each generated IOR and all error conditions. Currently - the NotFound exception is tested for. + the NotFound exception is tested for. diff --git a/TAO/tests/InterOp-Naming/README b/TAO/tests/InterOp-Naming/README index 296e8b9cd5a..7f9a3abd77c 100644 --- a/TAO/tests/InterOp-Naming/README +++ b/TAO/tests/InterOp-Naming/README @@ -1,3 +1,5 @@ +$Id$ + CORBA InterOperable Naming Service : ------------------------------------- @@ -13,12 +15,12 @@ $(TAO_ROOT)/docs/Options.html The InterOp_test : The test server adds the argument specified with the -i option and the -IOR of the INS_i servant to the IOR table. The test client calls +IOR of the INS_i servant to the IOR table. The test client calls resolve_initial_references on argv[1]. TEST 1: Single Profile corbalocs using -ORBInitRef -InterOp-Naming> INS_test_server -i ins -nd -ORBObjRefStyle URL +InterOp-Naming> INS_test_server -i ins -nd -ORBObjRefStyle URL // -i Adds the ins:IOR mapping to // the ORB table. // -n Use the Naming Service. @@ -29,7 +31,7 @@ InterOp-Naming> INS_test_client arbit_service \ TEST 2: Multiple Profile corbalocs using -ORBInitRef -InterOp-Naming> INS_test_server -i ins -nd -ORBobjrefstyle url +InterOp-Naming> INS_test_server -i ins -nd -ORBobjrefstyle url // -i Adds the ins:IOR mapping to // the ORB table. @@ -43,7 +45,7 @@ InterOp-Naming> INS_test_client arbit_service \ TEST 3: Single Profile corbaloc using -ORBDefautlInitRef -InterOp-Naming> INS_test_server -i ins -nd -ORBObjRefStyle URL +InterOp-Naming> INS_test_server -i ins -nd -ORBObjRefStyle URL // -i Adds the ins:IOR mapping to // the ORB table. @@ -54,7 +56,7 @@ InterOp-Naming> INS_test_client ins \ TEST 4: Multiple Profile corbaloc using -ORBDefaultInitRef -InterOp-Naming> INS_test_server -i ins -nd -ORBobjrefstyle url +InterOp-Naming> INS_test_server -i ins -nd -ORBobjrefstyle url // -i Adds the ins:IOR mapping to // the ORB table. diff --git a/TAO/tests/MT_Client/README b/TAO/tests/MT_Client/README index 64e499a3524..1b003acdb87 100644 --- a/TAO/tests/MT_Client/README +++ b/TAO/tests/MT_Client/README @@ -1,10 +1,9 @@ - -# $Id$ +$Id$ Description: This is a simple test for multi-threaded clients; it just -creates a simple server process and runs a client with multiple thread +creates a simple server process and runs a client with multiple thread sharing the same object reference. Expected output: diff --git a/TAO/tests/MT_NoUpcall_Client_Leader/README b/TAO/tests/MT_NoUpcall_Client_Leader/README index f8174c18bc2..bb44e5784dc 100644 --- a/TAO/tests/MT_NoUpcall_Client_Leader/README +++ b/TAO/tests/MT_NoUpcall_Client_Leader/README @@ -1,4 +1,4 @@ -// $Id$ +$Id$ The test simulates a case when an incomming requests is being detected while a client-leader thread is waiting in the reactor event loop for its own reply. @@ -16,14 +16,14 @@ in the reactor event loop for its own reply. Thus, if any follower threads are available, they can pick it up and process it eventually. A rapidly increasing spin prevention back-off delay helps to mitigate the -negative influence of this solution over the processor utilization. +negative influence of this solution over the processor utilization. Run the test by starting the server: ./server -ORBSvcConf mt_noupcall.conf - + And the client: ./client - + If any requests get "ignored" the server process will hang indefinitely. diff --git a/TAO/tests/MT_Server/README b/TAO/tests/MT_Server/README index 7820727a22f..4aea64dae68 100644 --- a/TAO/tests/MT_Server/README +++ b/TAO/tests/MT_Server/README @@ -1,9 +1,9 @@ -# $Id$ +$Id$ Description: This is a simple test for a thread-pool server. It creates a -server process with a variable number of threads, multiple clients can +server process with a variable number of threads, multiple clients can send requests to it, the requests are handled in different threads. Expected output: diff --git a/TAO/tests/OBV/Any/README b/TAO/tests/OBV/Any/README index d8242a24fc1..9f8e26e7bef 100644 --- a/TAO/tests/OBV/Any/README +++ b/TAO/tests/OBV/Any/README @@ -1,9 +1,11 @@ /** +$Id$ + @page OBV/Any Test README File - This is a very simple test to show and verify basic OBV-and-Any - functionality. + This is a very simple test to show and verify basic OBV-and-Any + functionality. To run the test either use the run_test.pl script: diff --git a/TAO/tests/OBV/Forward/README b/TAO/tests/OBV/Forward/README index 4ab2e6d3fdc..deab3103ab0 100644 --- a/TAO/tests/OBV/Forward/README +++ b/TAO/tests/OBV/Forward/README @@ -1,9 +1,11 @@ /** +$Id$ + @page OBV/Forward Test README File - This is a very simple test to show and verify - forward declaration of valuetypes. + This is a very simple test to show and verify + forward declaration of valuetypes. To run the test either use the run_test.pl script: diff --git a/TAO/tests/OBV/README b/TAO/tests/OBV/README index a6796ec644d..568d07d64f6 100644 --- a/TAO/tests/OBV/README +++ b/TAO/tests/OBV/README @@ -1,4 +1,4 @@ -// $Id$ +$Id$ The following TAO applications test and illustate various Object By Value (OBV or valuetypes) functionality and their usage scenarios. @@ -9,7 +9,7 @@ By Value (OBV or valuetypes) functionality and their usage scenarios. of valuetypes inside CORBA Any type. . Factory - + The example tests OBV factory construct. . Forward diff --git a/TAO/tests/OBV/TC_Alignment/README b/TAO/tests/OBV/TC_Alignment/README index dc1a595747e..0c747c84158 100644 --- a/TAO/tests/OBV/TC_Alignment/README +++ b/TAO/tests/OBV/TC_Alignment/README @@ -1,5 +1,7 @@ /** +$Id$ + @page OBV/TC_ALignment Test README File This is a test of the traversal of the typecode tree for valuetypes. @@ -11,7 +13,7 @@ an 8-byte boundary. This problem has been fixed - the test is to ensure that the problem does not recur as a result of future changes to the TAO TypeCode class. - Four valuetypes are declared in an IDL file, named in such a way + Four valuetypes are declared in an IDL file, named in such a way that their repository IDs (including the terminal null byte) have lengths of 25, 27, 29, and 31. The test method is called 4 times. In each call, one of these valuetypes is inserted into an Any and returned to the client, diff --git a/TAO/tests/ORB_init/Portspan/README b/TAO/tests/ORB_init/Portspan/README index 8eb4f91abd0..cdfc626f004 100644 --- a/TAO/tests/ORB_init/Portspan/README +++ b/TAO/tests/ORB_init/Portspan/README @@ -1,16 +1,16 @@ - $Id$ +$Id$ portspan Test ------------- The portspan test verifies that the portspan option to the ORB_init() call -behaves correctly. This option allows you to restrict the port that a +behaves correctly. This option allows you to restrict the port that a server-side ORB will use to listen for IIOP requests, from a given range of port numbers, starting at a given initial port. The test works by starting a simple ORB on an endpoint with a portspan of 2. server -ORBEndpoint iiop://:5555/portspan=2 The test script does this three times and reports an error if the first two -don't succeed, or if the third call doesn't fail. +don't succeed, or if the third call doesn't fail. diff --git a/TAO/tests/ORB_shutdown/README b/TAO/tests/ORB_shutdown/README index 8fc118e49db..3a701dcc060 100644 --- a/TAO/tests/ORB_shutdown/README +++ b/TAO/tests/ORB_shutdown/README @@ -1,9 +1,11 @@ /** +$Id$ + @page ORB_shutdown Test README File The simplest possible test for TAO's shutdown procedure. This -test is basically a regression for BUG 1265. Please see BUG 1265 in +test is basically a regression for BUG 1265. Please see BUG 1265 in http://deuce.doc.wustl.edu/bugzilla/show_bug.cgi?id=1265 diff --git a/TAO/tests/Ondemand_Write/README b/TAO/tests/Ondemand_Write/README index ee77329decb..dec8197b103 100644 --- a/TAO/tests/Ondemand_Write/README +++ b/TAO/tests/Ondemand_Write/README @@ -1,5 +1,7 @@ /** +$Id$ + @page Hello Test README File The simplest possible test for TAO. This is a very simple @@ -26,7 +28,7 @@ anything useful, i.e. chances are that this test will always pass. type codes or Anys. Please refrain from "improving", extending or expanding this -test, if you need to change +test, if you need to change To run the test use the run_test.pl script: diff --git a/TAO/tests/Param_Test/README b/TAO/tests/Param_Test/README index 3bd468d2ff3..b53c2e9d7eb 100644 --- a/TAO/tests/Param_Test/README +++ b/TAO/tests/Param_Test/README @@ -1,17 +1,4 @@ -// $Id$ - -// ============================================================================ -// -// = LIBRARY -// TAO/tests/Param_Test -// -// = FILENAME -// README -// -// = AUTHOR -// Aniruddha Gokhale -// -// ============================================================================ +$Id$ This directory contains an application that tests all the parameter passing conventions in CORBA for a number of OMG IDL data types. @@ -35,7 +22,7 @@ To run the server, type arguments to ORB_init start with the letters -ORB. Please see TAO documentattion on all the supported arguments - -d for debugging. + -d for debugging. -o <ior_output_file> for outputting the servant IOR to a file. To run the client, type @@ -47,7 +34,7 @@ To run the client, type [-d] debugging [-n loopcount] number of times to run the test [-f servant-IOR-file] reads the servant-IOR from the - specified file. + specified file. [-k Param_Test-obj-ref-key] object key of Param_Test object [-i invocation (sii/dii)] default is static invocation interface. To use DII, type @@ -91,7 +78,7 @@ the client: 1. Using the -f option to read the IOR from a file. - 2. Using the -k option to read the IOR from the + 2. Using the -k option to read the IOR from the command line. run_test.pl: @@ -99,8 +86,8 @@ run_test.pl: There is a perl script in this directory named run_test.pl to test all the types. It starts the server first and then runs the client with the different data type parameters. The - arguments it takes are: - + arguments it takes are: + -n num -- runs the client num times (default is 5) -d -- runs each in debug mode -onewin -- keeps all tests in one window on NT diff --git a/TAO/tests/Portable_Interceptors/Bug_2133/README b/TAO/tests/Portable_Interceptors/Bug_2133/README index b2d570b8158..343f8b57a61 100644 --- a/TAO/tests/Portable_Interceptors/Bug_2133/README +++ b/TAO/tests/Portable_Interceptors/Bug_2133/README @@ -2,7 +2,7 @@ $Id$ This test attempts to contact a server IOR with no connectable profile in it (on account of how there is no server running). -The method invocation should fail but the installed client request interceptor should have its send_request and receive_exception methods invoked regardless. +The method invocation should fail but the installed client request interceptor should have its send_request and receive_exception methods invoked regardless. The expected result looks like: diff --git a/TAO/tests/Portable_Interceptors/PolicyFactory/README b/TAO/tests/Portable_Interceptors/PolicyFactory/README index b9ba6219524..2cf03ef8c49 100644 --- a/TAO/tests/Portable_Interceptors/PolicyFactory/README +++ b/TAO/tests/Portable_Interceptors/PolicyFactory/README @@ -1,4 +1,4 @@ -# $Id$ +$Id$ This test verifies that PolicyFactory support is working properly. Working PolicyFactory support requires the following on the server side: @@ -22,5 +22,5 @@ Run the test as follows: Output should be very similar to the following: ==== Running PolicyFactory test - + PolicyFactory test succeeded. diff --git a/TAO/tests/Strategies/README b/TAO/tests/Strategies/README index d6116565696..711b37b29c6 100644 --- a/TAO/tests/Strategies/README +++ b/TAO/tests/Strategies/README @@ -1,11 +1,11 @@ -// $Id$ +$Id$ This test helps show the various ways in which the default and -advanced TAO Strategies can be dynamically loaded. +advanced TAO Strategies can be dynamically loaded. The default TAO strategies are defined in tao/default_resource.cpp and the advanced TAO strategies are defined in -tao/Strategies/advanced_resource.cpp. +tao/Strategies/advanced_resource.cpp. The advanced TAO strategies can be loaded dynamically or statically linked. To load these strategies dynamically, we need to @@ -14,7 +14,7 @@ statically, we need to link the library and include the header file. This test shows a simple case where in only the default strategies are used. It also shows the advanced case where in the -advanced strategies are used. +advanced strategies are used. The test can be run using the perl script available or manually. |