Skip to content

Handle duplicate connection outputs in TOUGH3 and zombie subprocesses #182

Handle duplicate connection outputs in TOUGH3 and zombie subprocesses

Handle duplicate connection outputs in TOUGH3 and zombie subprocesses #182

Triggered via pull request January 9, 2024 14:24
@keurfonluukeurfonluu
synchronize #160
devel
Status Failure
Total duration 1m 29s
Artifacts

ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 5 warnings
build (3.8)
Process completed with exit code 1.
build (3.7)
The operation was canceled.
build (3.10)
The operation was canceled.
build (3.9)
The operation was canceled.
build (3.11)
The operation was canceled.
build (3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/