Wrapper State test
Test Objectives
- Verify that the wrapper is capable is generating a state file.
- Verify that the state file can be used to complete the dataPipeline.
APIs affected by this test
- All APIs are exercised via a dataPipeline command.
Setup
- ligotools package is required for running this test. Check that it is mounted
- Install the following tests script in a directory on your local machine or the ldas system
- S2 frame files must be mounted on ldas system and known to diskcacheAPI:
Test Execution
cd <your scripts directory>
Usage: wrapperstate.tcl [options] >& wrapperstate.log &
| Option
| Description
|
<-s>
| ldas site e.g. dev, lho, ldas-suntest3
|
e.g.
wrapperstate.tcl -s dev >& wrapperstate.log &
Test Validation:
The script issues a dataPileine job to direct the wrapper to output a state file.
After obtaining the state file, a second dataPipeline is submitted with the state file
to direct the dataPipeline to complete processing. The DSO /ldas/lib/wrapperAPI/libstate.so
is used for testing so there are no products generated at the end. But this test
demonstrates a state file from the wrapper is generated and ldas can accept the state file
as input.
Expect 2 jobs to complete successfully:
e.g.
LDAS-DEV31915268
Subject:
LDAS-DEV31915268 state test
Your results:
LDAS-DEV31915268State.ilwd
can be found at:
/ldas_outgoing/jobs/LDAS-DEV_3191/LDAS-DEV31915268
...
LDAS-DEV31915272
Subject:
LDAS-DEV31915272 state test
LDAS-DEV31915272 produced no products
...