An error occurred while fetching the pipelines jobs.

Add LICENSE

7 jobs for master in 12 minutes and 47 seconds (queued for 1 minute and 9 seconds)

Group jobs by

Build

Test

Status	Job	Stage	Name	Duration	Coverage
No jobs to show

Name Stage Failure

	Name	Stage	Failure
failed	code_intelligence_go	Test
	`go get -t github.com/labstack/echo/v4@v4.1.16 missing go.sum entry for module providing package github.com/stretchr/testify/require (imported by github.com/labstack/echo/v4); to add: go get -t github.com/labstack/echo/v4@v4.1.16 Uploading artifacts for failed job Uploading artifacts... WARNING: dump.lsif: no matching files ERROR: No files to upload Cleaning up project directory and file based variables ERROR: Job failed: exit code 1`

failed

code_intelligence_go

Test

	go get -t github.com/labstack/echo/v4@v4.1.16
missing go.sum entry for module providing package github.com/stretchr/testify/require (imported by github.com/labstack/echo/v4); to add:
	go get -t github.com/labstack/echo/v4@v4.1.16
Uploading artifacts for failed job
Uploading artifacts...
WARNING: dump.lsif: no matching files              
ERROR: No files to upload                          
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

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