Skip to content

Require a database for Django to start #272

Require a database for Django to start

Require a database for Django to start #272

Triggered via pull request September 11, 2024 15:33
Status Success
Total duration 1m 18s
Artifacts 1

test.yaml

on: pull_request
unit-tests  /  Inclusive naming
12s
unit-tests / Inclusive naming
unit-tests  /  Shell scripts lint
4s
unit-tests / Shell scripts lint
unit-tests  /  Dockerfile lint
6s
unit-tests / Dockerfile lint
unit-tests  /  Lint metadata.yaml
3s
unit-tests / Lint metadata.yaml
unit-tests  /  Lint and unit tests
59s
unit-tests / Lint and unit tests
unit-tests  /  Draft publish docs
17s
unit-tests / Draft publish docs
unit-tests  /  Check license headers
25s
unit-tests / Check license headers
unit-tests  /  Check libraries
3s
unit-tests / Check libraries
unit-tests  /  Required Test Status Checks
0s
unit-tests / Required Test Status Checks
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
unit-tests / Check libraries
No lib folder detected. Skipping action.
unit-tests / Shell scripts lint
The following actions use a deprecated Node.js version and will be forced to run on node20: lumaxis/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
unit-tests / Check license headers
Restore cache failed: Some specified paths were not resolved, unable to cache dependencies.

Artifacts

Produced during runtime
Name Size
report Expired
1.1 KB