failed Pipeline #36037 triggered by
Lorenz Kapsner
@lorenz.kapsner

docs: updated documentation

3 jobs for latest in 50 seconds (queued for 1 second)
Loading
Name Stage Failure
failed
check Build
1 error ✖ | 0 warnings ✔ | 0 notes ✔
Error: R CMD check found ERRORs
Execution halted
Uploading artifacts for failed job
Uploading artifacts...
/builds/sNoqxZaP/0/miracum/dqa/dqastats/ci/*.Rcheck: found 96 matching files and directories

Uploading artifacts as "archive" to coordinator... ok
id=158201 responseStatus=201 Created token=uLHuYUCB
Cleaning up project directory and file based variables
ERROR: Job failed: exit code 1

failed
testing Build
  Bad credentials

Rate limit remaining: 59/60
Rate limit reset at: 2022-02-04 19:54:53 UTC


Execution halted
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.