Nighly build #707
nightly.yaml
on: schedule
Matrix: linux-arm64
Matrix: linux
macOS x86_64 pak binaries
46m 59s
Windows pak binaries
52m 41s
macos arm64 pak binaries
0s
Parameters
1s
deploy
8m 47s
Annotations
9 errors, 2 warnings, and 2 notices
macos arm64 pak binaries
The self-hosted runner: pak-macos-arm64 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
Linux static pak binaries for R 3.4, linux/arm64
The self-hosted runner: linux-arm64 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
Linux static pak binaries for R 3.5, linux/arm64
The self-hosted runner: linux-arm64 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
Linux static pak binaries for R 3.6, linux/arm64
The self-hosted runner: linux-arm64 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
Linux static pak binaries for R 4.0, linux/arm64
The self-hosted runner: linux-arm64 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
Linux static pak binaries for R 4.1, linux/arm64
The self-hosted runner: linux-arm64 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
Linux static pak binaries for R 4.2, linux/arm64
The self-hosted runner: linux-arm64 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
Linux static pak binaries for R 4.4, linux/arm64
The self-hosted runner: linux-arm64 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
Linux static pak binaries for R 4.3, linux/arm64
The self-hosted runner: linux-arm64 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
deploy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
deploy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
deploy
Completed deployment successfully! ✅
|
deploy
Completed deployment successfully! ✅
|