Fix to remote-desktop #3188
Triggered via pull request
October 23, 2024 18:53
Status
Failure
Total duration
6h 0m 46s
Artifacts
–
build_push.yaml
on: pull_request
pre-build-checks
9s
Matrix: build-push
Annotations
7 errors and 3 warnings
build-push (jupyterlab-cpu)
Process completed with exit code 1.
|
build-push (jupyterlab-pytorch)
Process completed with exit code 1.
|
build-push (remote-desktop)
Process completed with exit code 1.
|
build-push (sas)
The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 360 minutes.
|
build-push (sas)
The operation was canceled.
|
build-push (rstudio)
The job running on runner GitHub Actions 13 has exceeded the maximum execution time of 360 minutes.
|
build-push (rstudio)
The operation was canceled.
|
build-push (jupyterlab-cpu)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/docker-login@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
build-push (jupyterlab-pytorch)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/docker-login@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
build-push (remote-desktop)
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/docker-login@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|