failed Pipeline #103367 triggered by
Antonio M. Caceres
@acaceres

Change capitalization of constants and of struct variables in game.c.

5 jobs for master in 0 seconds (queued for 74 minutes and 35 seconds)
Status Name Job ID Coverage
  Test
failed body #319356

failed list #319352

failed polygon #319354

failed scene #319355

failed vector #319353

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