Skip to content

Provide remote Pyro5 compatibility for multiple remote objects #199

Provide remote Pyro5 compatibility for multiple remote objects

Provide remote Pyro5 compatibility for multiple remote objects #199

Triggered via pull request November 15, 2024 15:52
Status Failure
Total duration 36s
Artifacts

ci.yml

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

Annotations

1 error and 2 warnings
3.x
Process completed with exit code 2.
3.x
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/
3.x
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/