failed Pipeline #46659 triggered by
Ethan Ordentlich
@eordentl

error messages go brrr

4 jobs for tests in 0 seconds (queued for 82 minutes and 26 seconds)
Status Name Job ID Coverage
  Test
failed A #151753

failed B #151754

failed C #151755

failed static #151752

 
Name Stage Failure
failed
C Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
B Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
A Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
failed
static Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log

Speed up your pipelines with Needs relationships

Using the needs keyword makes jobs run before their stage is reached. Jobs run as soon as their needs relationships are met, which speeds up your pipelines.

If you add needs to jobs in your pipeline you'll be able to view the needs relationships between jobs in this tab as a Directed Acyclic Graph (DAG).

There are no test reports for this pipeline

You can configure your job to use unit test reports, and GitLab displays a report here and in the related merge request.