Project 'rfhf19/cleanning-portalmec' was moved to 'rfhferreira/cleanning-portalmec'. Please update any links and bookmarks that may still have the old path.
failed Pipeline #31120 triggered by
ahcv19
@ahcv19

getting vm version

1 job for issue/16-get-vm-version in 3 minutes and 46 seconds (queued for 4 seconds)
Status
Job
Stage
Name
Duration
Coverage
No jobs to show
Name Stage Failure
failed
test Test
/usr/local/bundle/gems/bundler-2.3.24/lib/bundler/cli.rb:25:in `start'
/usr/local/bundle/gems/bundler-2.3.24/exe/bundle:48:in `block in <top (required)>'
/usr/local/bundle/gems/bundler-2.3.24/lib/bundler/friendly_errors.rb:120:in `with_friendly_errors'
/usr/local/bundle/gems/bundler-2.3.24/exe/bundle:36:in `<top (required)>'
/usr/local/bundle/bin/bundle:23:in `load'
/usr/local/bundle/bin/bundle:23:in `<main>'
(See full trace by running task with --trace)
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).

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.