lsync test

Test Objectives

Verify lsync.tcl and its shared objects can generate same frame cache content given the same mount points as diskcacheAPI.

This is a standalone test, no APIs are affected by this test but the diskcacheAPI is used for cache comparison

The test does the following:

Untar the lsync tar ball in the local directory, or if a directory is specified, cd to that directory.
cd to the directory created by the untar process
Updates lsync.rsc with the ::MOUNT_PT variable from diskcacheAPI.
Invokes lsync.tcl to generate a cache file lsync.cache.
Compares current diskcacheAPI frame cache to lsync.cache; the test passes if the directories are the same.

Setup

Download an lsync tarball to be tested to a directory on the machine that the diskcacheAPI resides or login to the diskcacheAPI machine if the tarball is visible there.
Install the following tests script:
- lsync.test

Make sure the mount points are accessible.


        Make sure the frame cache is current by forcing a frame cache rebuild via cmonClient Utilities
        Rebuild frame disk cache


        
        Test Execution
        On the diskcacheAPI host 
        
Make sure there are no jobs running that would generate frame files as output.
		
cd <your directory containing script >

		
        Usage:  

        

            
                Option
                Description
			

                <tarball file path or directory containing lsync files>
                supply a tarball path or a directory containing lsync files and objects
        

        e.g. with tarball path

            lsync.test /ldas_outgoing/nightly_tarballs/lsync-SunOS-sun4u-1.2.39.tar.gz >& lsynctest.log &
            
        or with a specified directory 
            lsync.test lsync-SunOS-sun4u-1.2.36 >& lsynctest.log &
            
		
		
Test Validation:
        
        Verify that there are no errors with lsync.tcl run from the log file lsync.out in lsync files and objects directory.
        Verify that the test passes because there are not difference in cache directories.
        Example of output of an lsync.test that passes:
        

        working in /usr1/ldas/lsync-SunOS-sun4u-1.2.36
        running lsync.tcl 21005
        killing lsync.tcl 21005, 21005 /bin/sh ./runner.sh lsync.tcl
        killing lsync.tcl 21006, 21006 tclsh lsync.tcl
        cacheDump errors 
        cacheDump.py errors 
        difference between diskcacheAPI cache and lsync cache
        1,8d0
        < 
        < NOTE: cacheDump assumes that the LDAS runtime is installed
        < under /ldas_outgoing, and will not run if the LDASapi.rsc
        < and LDASdiskcache.rsc are not found!
        < 
        < reading /ldas_outgoing/diskcacheAPI/.frame.cache2
        < this can take a while, please be patient!!
        < DONE!
        child process exited abnormally
        TEST PASSED
         
         
         Examples of failed lsync test:
         

         working in /usr1/ldas/lsync-SunOS-sun4u-1.2.36
         running lsync.tcl 7175
         killing lsync.tcl 7176,  7176 tclsh lsync.tcl
         killing lsync.tcl 7175,  7175 /bin/sh ./runner.sh lsync.tcl
         cacheDump errors 
         cacheDump.py errors 
         difference between diskcacheAPI cache and lsync cache
        1,8d0
        < 
        < NOTE: cacheDump assumes that the LDAS runtime is installed
        < under /ldas_outgoing, and will not run if the LDASapi.rsc
        < and LDASdiskcache.rsc are not found!
        < 
        < reading /ldas_outgoing/diskcacheAPI/.frame.cache2
        < this can take a while, please be patient!!
        < DONE!
        231c223
        < /scratch/frames/S3_RDS/LHO,H,RDS_R_L1,1,16 1097712130 72 {751800016 751801168}
        ---
        > /scratch/frames/S3_RDS/LHO,H,RDS_R_L1,1,16 1097712093 69 {751800016 751801120}
        233c225
        < /scratch/frames/S3_RDS/LLO,L,RDS_R_L1,1,16 0 121 {751800016 751801952}
        ---
        > /scratch/frames/S3_RDS/LLO,L,RDS_R_L1,1,16 1097712096 116 {751800016 751801872}
        child process exited abnormally
        TEST FAILED