Skip to content
tests

improved ftest, but still couldn't manage to reproduce some bug #26

Sign in to view logs

improved ftest, but still couldn't manage to reproduce some bug

improved ftest, but still couldn't manage to reproduce some bug #26

Triggered via push September 6, 2023 22:37
@tobixentobixen
pushed 190fa54
master
Status Success
Total duration 41s
Artifacts –

tests.yaml

on: push
docs
21s
docs
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
docs
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
3.9
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
3.11
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
3.10
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/