Skip to content

GitLab

seemingly working version of the code

2 jobs for master in 13 seconds (queued for 9 seconds)
latest
95e04f3e
1 related merge request: !264 Assignment 4: Memory Allocator P4214 Sarzhevskii Ivan
Status Job ID Name Coverage
  Check
failed #197033
linter

00:00:13

 
  Test
skipped #197034
test
 
Name Stage Failure
failed
linter Check There has been a runner system failure, please try again 
Will be retried in 3s ...
Using Docker executor with image generic-c ...
WARNING: Failed to pull image with policy "never": Error: No such image: generic-c (manager.go:160:0s)
ERROR: Preparation failed: failed to pull image "generic-c" with specified policies [never]: Error: No such image: generic-c (manager.go:160:0s)
Will be retried in 3s ...
Using Docker executor with image generic-c ...
WARNING: Failed to pull image with policy "never": Error: No such image: generic-c (manager.go:160:0s)
ERROR: Preparation failed: failed to pull image "generic-c" with specified policies [never]: Error: No such image: generic-c (manager.go:160:0s)
Will be retried in 3s ...
ERROR: Job failed (system failure): failed to pull image "generic-c" with specified policies [never]: Error: No such image: generic-c (manager.go:160:0s)

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