Skip to content
CI

The cpu to query can now be specified #59

Sign in to view logs

The cpu to query can now be specified

The cpu to query can now be specified #59

Triggered via pull request September 12, 2024 22:24
@andrewjj20andrewjj20
opened #20
andrewjj20:specify_cpu
Status Success
Total duration 2m 24s
Artifacts –

ci.yml

on: pull_request
lint
27s
lint
Matrix: Build documentation
Matrix: Build and Test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build documentation (ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and Test (ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and Test (windows-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/