Skip to content
Unit tests (pyEpiabm)

Plotting cpp gibraltar #1456

Sign in to view logs

Plotting cpp gibraltar

Plotting cpp gibraltar #1456

Triggered via pull request September 25, 2023 14:15
@KCGallagherKCGallagher
opened #221
plotting-cpp-gibraltar
Status Success
Total duration 1m 23s
Artifacts –

unit-tests.yml

on: pull_request
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build-and-test (3.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-and-test (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-and-test (3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-and-test (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/