failed Pipeline #113609 triggered by
Adam Blank
@blank

Update manifest.json

3 jobs for master in 0 seconds (queued for 118 minutes and 27 seconds)
latest
Status Name Job ID Coverage
  Test
failed A #350318

failed B #350319

failed D #350320

 
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
D 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.