`gitlab-org/gitlab` artifacts aren't uploaded due to `429 Too Many Requests ` and jobs fail as a result
Many jobs in the gitlab-org/gitlab
project fail because artifacts aren't uploaded and jobs fail as a result.
coverage/: found 5 matching files
4996 knapsack/: found 6 matching files
4997 rspec_flaky/: found 4 matching files
4998 rspec_profiling/: found 1 matching files
4999 WARNING: tmp/capybara/: no matching files
5000 tmp/memory_test/: found 2 matching files
5001 WARNING: Uploading artifacts to coordinator... failed id=336960885 responseStatus=429 Too Many Requests status=429 Too Many Requests token=2jKruRbt
5002 WARNING: Retrying... error=invalid argument
5003 WARNING: Uploading artifacts to coordinator... failed id=336960885 responseStatus=429 Too Many Requests status=429 Too Many Requests token=2jKruRbt
5004 WARNING: Retrying... error=invalid argument
5005 WARNING: Uploading artifacts to coordinator... failed id=336960885 responseStatus=429 Too Many Requests status=429 Too Many Requests token=2jKruRbt
5006 FATAL: invalid argument
5008 ERROR: Job failed: exit code 1
Examples:
- https://gitlab.com/gitlab-org/gitlab/-/jobs/336960885#L4994
- https://gitlab.com/gitlab-org/gitlab/-/jobs/336960819
- https://gitlab.com/gitlab-org/gitlab/-/jobs/336960838
In these examples, the runners in use are private-runners-manager-3.gitlab.com
and private-runners-manager-4.gitlab.com
.