update tester

2 jobs for master in 52 seconds (queued for 6 seconds)

Status	Job ID	Name
Check
passed	#85224	linter	00:00:27 2 years ago

Test
failed	#85225	test	00:00:25 2 years ago

Name Stage Failure

	Name	Stage	Failure
failed	test	Test
	`Checking out 47006f74 as master... Skipping Git submodules setup Executing "step_script" stage of the job script Using docker image sha256:befec68140fd26f94121dcdc8b3efc390b78b305aa84737a7b3340c26727a79f for generic-c ... $ ./run-tests /usr/bin/bash: line 118: ./run-tests: No such file or directory Cleaning up project directory and file based variables ERROR: Job failed: exit code 1`

failed

test

Test

Checking out 47006f74 as master...

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:befec68140fd26f94121dcdc8b3efc390b78b305aa84737a7b3340c26727a79f for generic-c ...
$ ./run-tests
/usr/bin/bash: line 118: ./run-tests: No such file or directory
Cleaning up project directory and file based variables
ERROR: Job failed: exit code 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