| Name | Stage | Failure | ||
|---|---|---|---|---|
|
failed
|
forces | Test | There has been a timeout failure or the job got stuck. Check your timeout limits or try again | |
|
||||
|
failed
|
vector | Test | There has been a timeout failure or the job got stuck. Check your timeout limits or try again | |
|
||||
|
failed
|
list | Test | There has been a timeout failure or the job got stuck. Check your timeout limits or try again | |
|
||||
|
failed
|
polygon | Test | There has been a timeout failure or the job got stuck. Check your timeout limits or try again | |
|
||||
|
failed
|
scene | Test | There has been a timeout failure or the job got stuck. Check your timeout limits or try again | |
|
||||
|
failed
|
body | Test | There has been a timeout failure or the job got stuck. Check your timeout limits or try again | |
|
||||
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).
You can configure your job to use unit test reports, and GitLab displays a report here and in the related merge request.