Arvados

The big picture here is:

Started by upstream project "arvados-cwl-conformance-tests" build number 1566
originally caused by:
 Started by upstream project "docker-arvbox" build number 5372
 originally caused by:
  Started by upstream project "docker-jobs-image" build number 3120
  originally caused by:
   Started by upstream project "build-packages-multijob" build number 3993
   originally caused by:
    Started by upstream project "build-packages-python-ruby" build number 2831
    originally caused by:
     Started by upstream project "run-tests" build number 6346

docker-arvbox builds a Docker image and uploads it to Docker Hub. Later arvados-cwl-conformance-tests pulls that: Jenkins runs sdk/cwl/test_with_arvbox.sh which runs arvbox start $config $tag (where $tag is the Git commit hash) which runs docker run … arvados/arvbox-demo$TAG which implicitly pulls from Docker Hub and can fail:

+ arvbox start localdemo 6d7ad47255a49c583f2fb0d78e6df5029c9ba56b
Unable to find image 'arvados/arvbox-demo:6d7ad47255a49c583f2fb0d78e6df5029c9ba56b' locally
Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
+ docker cp -L /tmp/workspace/arvados-cwl-conformance-tests/label/build/pythoncmd/python3/suite/integration/sdk/cwl/tests cwltest:/usr/src/arvados/sdk/cwl
Error: No such container:path: cwltest:/usr/src/arvados/sdk
+ arvbox pipe
Error: No such container: cwltest
+ CODE=1
+ docker cp -L cwltest:/tmp/badges /tmp/workspace/arvados-cwl-conformance-tests/label/build/pythoncmd/python3/suite/integration/sdk/cwl/badges
Error: No such container:path: cwltest:/tmp/badges
+ test 0 = 0
+ arvbox stop
+ exit 1
Build step 'Execute shell' marked build as failure
Sending e-mails to: dev@arvados.org brett.smith@curii.com
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: FAILURE

This isn't totally our fault. But it's a little frustrating that we just built the arvbox image on another node. In principle there should be no need to re-download it from Docker Hub. We should be able to load it as a build artifact or something.