Deploy Nightly #2252
Triggered via schedule
November 30, 2025 03:17
WebFreak001
Status
Failure
Total duration
1d 0h 0m 2s
Artifacts
–
Annotations
2 errors and 5 warnings
|
Deploy nightly (windows-latest, x86)
Process completed with exit code 1.
|
|
Deploy nightly (ubuntu-20.04, x86_64)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Deploy nightly (macos-latest, arm64-apple-macos, arm64, release, 1)
This action no longer uses the GITHUB_TOKEN environment variable. You can simply remove the environment variable if it's `${secrets.GITHUB_TOKEN}` or migrate to setting `with: token: ...` instead. Setting this environment variable will be ignored in the future.
|
|
Deploy nightly (macos-latest, arm64-apple-macos, arm64, release, 1)
This action no longer uses the GITHUB_TOKEN environment variable. You can simply remove the environment variable if it's `${secrets.GITHUB_TOKEN}` or migrate to setting `with: token: ...` instead. Setting this environment variable will be ignored in the future.
|
|
Deploy nightly (macos-latest, x86_64)
This action no longer uses the GITHUB_TOKEN environment variable. You can simply remove the environment variable if it's `${secrets.GITHUB_TOKEN}` or migrate to setting `with: token: ...` instead. Setting this environment variable will be ignored in the future.
|
|
Deploy nightly (macos-latest, x86_64)
This action no longer uses the GITHUB_TOKEN environment variable. You can simply remove the environment variable if it's `${secrets.GITHUB_TOKEN}` or migrate to setting `with: token: ...` instead. Setting this environment variable will be ignored in the future.
|
|
Deploy nightly (windows-latest, x86_64)
This action no longer uses the GITHUB_TOKEN environment variable. You can simply remove the environment variable if it's `${secrets.GITHUB_TOKEN}` or migrate to setting `with: token: ...` instead. Setting this environment variable will be ignored in the future.
|