Skip to content

Spurious failures caused by GitLab's 50x responses

Runners sometimes get HTTP 502 or 504 responses from GitLab. So far, I've found 5 symptoms:

  1. When cloning the repo under test, which is unrecoverable.
  2. When cloning submodules, in which case git automatically retries and may succeed.
  3. When fetching perf notes, which is unrecoverable.
  4. When pushing perf notes, in which case ci/test-metrics.sh retries and may succeed.
  5. When uploading job archives, in which case gitlab-runner retries and may succeed.
Edited by Bryan R
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information