Arvados

arvados-cwl-runner now implements enough functionalities that testing them manually is not viable.

Test that the following behaviours are preserved regardless of whether the job is run locally or submitted to arvados:

• If --project-uuid is specified, the pipeline instance, all child jobs, and all collections produced are placed in that project
• Jobs that have already been run (that the user has access to) are reused
  • If --ignore-docker-for-reuse is specified, jobs are reused regardless of the hash of the docker image

Test that the following flags, when called together, raise an error:

• --local --no-wait