Skip to content

Various fixes to ROCK files and integration tests. #70

Various fixes to ROCK files and integration tests.

Various fixes to ROCK files and integration tests. #70

Triggered via pull request July 29, 2024 16:18
Status Failure
Total duration 29m 18s
Artifacts

pull_request.yaml

on: pull_request
Build Rocks and Push Arch Specific Images  /  Get rocks
7s
Build Rocks and Push Arch Specific Images / Get rocks
Matrix: Build Rocks and Push Arch Specific Images / Build rock
Matrix: scan-images / Scan image
Waiting for pending jobs
run-tests  /  Run tests
run-tests / Run tests
Combine Rocks and Push Multiarch Manifest  /  Create Mulitarch Manifest
Combine Rocks and Push Multiarch Manifest / Create Mulitarch Manifest
Fit to window
Zoom out
Zoom in

Annotations

60 errors
Build Rocks and Push Arch Specific Images / Build rock (trivy-adapter-photon, v2.9.3, v2.9.3/trivy-adapter-photon, arm64, ghcr.io/canonical/t...
The self-hosted runner: openstack-arm-large-21-e307d55f1d8404c4d65f045e 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.
Build Rocks and Push Arch Specific Images / Build rock (harbor-jobservice, v2.6.3, v2.6.3/harbor-jobservice, arm64, ghcr.io/canonical/harbor-...
The self-hosted runner: openstack-arm-medium-52-5f944544f259f48fca29d8b3 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.
Build Rocks and Push Arch Specific Images / Build rock (harbor-db, v2.6.3, v2.6.3/harbor-db, arm64, ghcr.io/canonical/harbor-db:cb6f206eaac96...
The self-hosted runner: openstack-arm-large-20-dca162a9fc6e459c17c7721f 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.