Runner fails to download artifacts. Fails with "... was unexpected at this time"
With gitlab-ci-multi-runner-windows-amd64.exe version 1.4.0 we are seeing a problem that was not present with 1.1.4.
When jobs of one stage complete, the artifacts from jobs of the previous stage may not be downloaded. In the attached .gitlab-ci.yml file, the job "winBuild" creates artifacts needed by the job winSikuliNvidia. The winBuild job runs to successful completion, and the artifacts are persisted to the Gitlab server. However, when the job winSikuliNvidia is launched the following occurs:
Running with gitlab-ci-multi-runner 1.4.0 (5dd9b2fd) Using Shell executor... Running on VISSIMLAB-TEST...
Fetching changes...
HEAD is now at 611a4fb Testing CI Checking out 611a4fb0 as srs_osgEarth...
... was unexpected at this time.
ERROR: Build failed: exit status 255
This results in a failure of the job and stage. Examination of the file system on the runner reveals that the repo has been checked out, but none of the artifacts that should be there from the previous build stage have been fetched. It does not seem to have gotten to the point of running the yml yet, or is failing at first attempt.
Replacing the runner with version 1.1.4 corrects the problem. All runners are configured as "shell" runners. Host OS for the runners is Windows 7. Gitlab server is version 8.9.6.