Skip to content
tests

Handle configuration in db with new endpoints #338

Sign in to view logs

Handle configuration in db with new endpoints

Handle configuration in db with new endpoints #338

Triggered via pull request October 15, 2024 10:23
@stefanorosanellistefanorosanelli
synchronize #76
stefanorosanelli:feat/200-config-db-endpoints
Status Success
Total duration 1m 46s
Artifacts –

unit.yml

on: pull_request
Matrix: Run unit tests
finish
4s
finish
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Run unit tests (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run unit tests (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run unit tests (3.12.3)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
finish
The following actions use a deprecated Node.js version and will be forced to run on node20: coverallsapp/github-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/