chore: build-base, doc improvement and test fixes #1150
e2e_test.yaml
on: pull_request
End-to-End Test
0s
Matrix: deploy-e2e-test-runner
Annotations
14 errors and 2 warnings
Deploy End-to-End Test Runner (schedule)
Process completed with exit code 1.
|
Deploy End-to-End Test Runner (schedule)
Unable to download artifact(s): Artifact not found for name: dangerous-test-only-github-runner_ubuntu-22.04-amd64-arm64.charm
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
Deploy End-to-End Test Runner (pull_request)
The job was canceled because "schedule_sd" failed.
|
Deploy End-to-End Test Runner (pull_request)
The operation was canceled.
|
Deploy End-to-End Test Runner (workflow_dispatch)
The job was canceled because "schedule_sd" failed.
|
Deploy End-to-End Test Runner (workflow_dispatch)
The operation was canceled.
|
Deploy End-to-End Test Runner (workflow_dispatch)
Process completed with exit code 1.
|
Deploy End-to-End Test Runner (push)
The job was canceled because "schedule_sd" failed.
|
Deploy End-to-End Test Runner (push)
The operation was canceled.
|
Deploy End-to-End Test Runner (push)
Process completed with exit code 1.
|
Deploy End-to-End Test Runner (issues)
The job was canceled because "schedule_sd" failed.
|
Deploy End-to-End Test Runner (issues)
Process completed with exit code 1.
|
Deploy End-to-End Test Runner (issues)
The operation was canceled.
|
End-to-End Test
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
Build Charm
No files were found with the provided path: github-runner_ubuntu-22.04-amd64-arm64.charm. No artifacts will be uploaded.
|
Deploy End-to-End Test Runner (schedule)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: charmed-kubernetes/actions-operator@main. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|