Page History

...

• At job startup, the pipeline interface is invoked with the command: bash pipeline_wrapper (see for example: /sdf/data/fermi/n/u41/L1/logs/DEV/AAA-testVerifyS3df-no-wrap/5.9/verify/000/slurm_pilot)
• If we invoke the container with <job executable="${preamble} ${container_wrap} python --version" batchOptions="${extra}" /> (as in Brian's example), the pipeline interface defined in pipeline_wrapper is NOT available inside the container.

How to reproduce the issue

• The task Task AAA-testVerifyS3df-wrapper (see xml here) loads the container with ${container_wrap} at line line 50:
  • <job executable="${preamble} ${container_wrap} ${python27} ${L1ProcROOT}/verify.py" batchOptions="${extra}" />
• and loses Thereby losing access to the pipeline interface. For example, we try reading the variable pipelineSet, and this fails  and fail (full log here, error at line 180):
  • which: no pipelineSet in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)

• The task Task AAA-testVerifyS3df-no-wrap (see xml here)