Skip to content
CI

Update for Materials Project v2 API #412

Sign in to view logs

Update for Materials Project v2 API

Update for Materials Project v2 API #412

Triggered via pull request September 18, 2023 15:06
@matthewcarbonematthewcarbone
synchronize #190
pmgv2
Status Failure
Total duration 1m 42s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yml

on: pull_request
Matrix: Run unit testing suite
Run Black code quality check
16s
Run Black code quality check
Run flake8 code quality check
12s
Run flake8 code quality check
Check semantic version placeholder exists in the __init__
7s
Check semantic version placeholder exists in the __init__
Build documentation test
1m 27s
Build documentation test
Build and publish to PyPI
0s
Build and publish to PyPI
Build and publish documentation via GitHub Pages
0s
Build and publish documentation via GitHub Pages
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 8 warnings
Run unit testing suite (ubuntu-latest, 3.8)
Process completed with exit code 1.
Run unit testing suite (macOS-latest, 3.8)
The job was canceled because "ubuntu-latest_3_8" failed.
Run unit testing suite (macOS-latest, 3.8)
The operation was canceled.
Run unit testing suite (macOS-latest, 3.9)
The job was canceled because "ubuntu-latest_3_8" failed.
Run unit testing suite (macOS-latest, 3.9)
The operation was canceled.
Run unit testing suite (ubuntu-latest, 3.10)
The operation was canceled.
Run unit testing suite (ubuntu-latest, 3.11)
The operation was canceled.
Run unit testing suite (macOS-latest, 3.11)
The operation was canceled.
Run unit testing suite (macOS-latest, 3.10)
The operation was canceled.
Run unit testing suite (ubuntu-latest, 3.9)
The operation was canceled.
Run flake8 code quality check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, suo/flake8-github-action@releases/v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run unit testing suite (ubuntu-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run unit testing suite (ubuntu-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run unit testing suite (ubuntu-latest, 3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run unit testing suite (macOS-latest, 3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run unit testing suite (macOS-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run unit testing suite (ubuntu-latest, 3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build documentation test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/