failed Pipeline #103967 triggered by
Maxwell F. (Max) Chen
@mfchen

autocommit

4 jobs for master in 0 seconds (queued for 72 minutes and 56 seconds)
latest
Status Name Job ID Coverage
  Test
failed body #322064

failed collision #322065

failed forces #322066

failed scene #322067

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