test_dag_plot_ontology now generates svg instead of png #391
build_ci.yml
on: push
Matrix: build
Finish submitting coverage
4s
Annotations
13 errors and 8 warnings
build (windows-latest, 3.10)
Process completed with exit code 1.
|
build (windows-latest, 3.9)
Event loop is closed
|
build (windows-latest, 3.9)
Process completed with exit code 1.
|
build (ubuntu-latest, 3.11)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
build (ubuntu-latest, 3.11)
Process completed with exit code 143.
|
build (windows-latest, 3.11)
Process completed with exit code 1.
|
build (ubuntu-latest, 3.9)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
build (ubuntu-latest, 3.9)
Process completed with exit code 143.
|
build (ubuntu-latest, 3.10)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
build (ubuntu-latest, 3.10)
Process completed with exit code 143.
|
build (ubuntu-latest, 3.8)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
build (ubuntu-latest, 3.8)
Process completed with exit code 143.
|
build (windows-latest, 3.8)
The hosted runner: GitHub Actions 9 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
build (windows-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@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/
|
build (windows-latest, 3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@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/
|
build (ubuntu-latest, 3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@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/
|
build (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/
|
build (windows-latest, 3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@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/
|
build (ubuntu-latest, 3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@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/
|
build (ubuntu-latest, 3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@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/
|
build (ubuntu-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@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/
|