Update .gitlab-ci.yml

3 jobs for master in 7 seconds (queued for 1 second)

Test

Status	Name	Job ID
Test
failed	A	#361053	00:00:06 4 months ago
failed	B	#361054	00:00:06 4 months ago
passed	static	#361052	00:00:02 4 months ago

	Name	Stage
failed	B	Test
	`│ ├─ Random Tests 3 ✘ expected: <19709292> but was: <0> │ ├─ Random Tests 4 ✘ expected: <6358135> but was: <0> │ ├─ Random Tests 5 ✘ expected: <1297958> but was: <0> │ ├─ Random Tests 6 ✔ │ └─ Check for early termination ✘ expected: <1> but was: <0> └─ JUnit Vintage ✔ Running after_script Uploading artifacts for failed job ERROR: Job failed: exit status 1`
failed	A	Test
	`│ ├─ Test Problem2: 1 ✘ expected: <2> but was: <3> │ ├─ Test Problem2: 2 ✔ │ ├─ Test Problem2: 3 ✘ expected: <1> but was: <0> │ ├─ Test Problem2: 4 ✘ expected: <-17> but was: <-4> │ └─ Import & Usage Tests ✔ └─ JUnit Vintage ✔ Running after_script Uploading artifacts for failed job ERROR: Job failed: exit status 1`

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

Learn more about Needs relationships

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.

Learn how to upload pipeline test reports