Skip to content

ci fails with no way of getting the logs for failed run

Summary

When trying to update sassc ruby gem in gitlab, the ci job fails as expected, but there is no way see the logs for failure.

Job in question https://gitlab.com/pravi/gitlab/-/jobs/549080700 I could easily get logs for other failed jobs.

Steps to reproduce

This Merge Request fails but cannot see the failed logs !29187 (merged)

Example Project

Happens on https://gitlab.com/gitlab-org/gitlab/

What is the current bug behavior?

ci job times out after 1 hour

What is the expected correct behavior?

It should ideally fail before, rather than wait an hour, but even if it fails after 1 hour, it should upload the failed logs for debugging

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Results of GitLab application Check

Possible fixes

may be allow time to upload logs after timeout.