failed Pipeline #78030 triggered by
Adam Blank
@blank

Add imports

4 jobs for master in 0 seconds (queued for 89 minutes and 59 seconds)
Status Name Job ID Coverage
  Test
failed A #235049

failed B #235048

failed C #235047

failed static #235046

 
Name Stage Failure
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
B Test There has been a timeout failure or the job got stuck. Check your timeout limits or try again
No job log
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
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.