Skip to content

Feature charged ligands #85

Feature charged ligands

Feature charged ligands #85

Triggered via pull request November 18, 2024 21:43
Status Failure
Total duration 42m 58s
Artifacts

CI.yaml

on: pull_request
Check for style and formatting violations with Ruff
11s
Check for style and formatting violations with Ruff
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 3 warnings
Check for style and formatting violations with Ruff
Process completed with exit code 1.
Test on ubuntu-latest, Python 3.10
Process completed with exit code 1.
Test on ubuntu-latest, Python 3.11
The job was canceled because "ubuntu-latest_3_10" failed.
Test on ubuntu-latest, Python 3.11
The operation was canceled.
Test on ubuntu-latest, Python 3.12
The job was canceled because "ubuntu-latest_3_10" failed.
Test on ubuntu-latest, Python 3.12
The operation was canceled.
Check for style and formatting violations with Ruff
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
Check for style and formatting violations with Ruff
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test on ubuntu-latest, Python 3.10
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/