probe: does the install-test run on the rebuilt Gitea docker runner
Validate Helm Charts / Detect changed charts (pull_request) Successful in 10s
Validate Helm Charts / Resource quantities (pull_request) Successful in 8s
Validate Helm Charts / Build ${{ fromJSON(needs.detect-changed-charts.outputs.charts) }} (pull_request) Successful in 6s
Validate Helm Charts / Trivy config ${{ fromJSON(needs.detect-changed-charts.outputs.scan-charts) }} (pull_request) Successful in 24s
Validate Helm Charts / Install-test ${{ fromJSON(needs.detect-changed-charts.outputs.install-charts) }} (pull_request) Successful in 17m31s
Validate Helm Charts / Detect changed charts (pull_request) Successful in 10s
Validate Helm Charts / Resource quantities (pull_request) Successful in 8s
Validate Helm Charts / Build ${{ fromJSON(needs.detect-changed-charts.outputs.charts) }} (pull_request) Successful in 6s
Validate Helm Charts / Trivy config ${{ fromJSON(needs.detect-changed-charts.outputs.scan-charts) }} (pull_request) Successful in 24s
Validate Helm Charts / Install-test ${{ fromJSON(needs.detect-changed-charts.outputs.install-charts) }} (pull_request) Successful in 17m31s
Throwaway. Bumps cyberchef (fast baseline, comparable with GitHub) and freesailarr (nine containers, real Wireguard tunnel - the hardest case in the repo) so both enter the install-test matrix, and prints the runner's cgroup facts plus the k3s node log if it still fails.
This commit is contained in:
3 files changed
+24
-3
No files matched your search
@@ -332,10 +332,31 @@ jobs:
|
||||
: "${FREESAILARR_WG_KEY:?empty - check op://GitHub-Actions/freesailarr-mullvad-test-config/credential}"
|
||||
: "${FREESAILARR_WG_ADDRESSES:?empty - check op://GitHub-Actions/freesailarr-mullvad-test-config/ip-address}"
|
||||
echo "Both VPN values arrived non-empty."
|
||||
- name: "PROBE runner facts (throwaway branch only)"
|
||||
run: |
|
||||
echo "runner=${RUNNER_NAME:-?} os=${RUNNER_OS:-?} arch=${RUNNER_ARCH:-?} nproc=$(nproc)"
|
||||
free -m | head -2 || true
|
||||
df -h / | tail -1 || true
|
||||
docker info --format 'server={{.ServerVersion}} storage={{.Driver}} cgroupDriver={{.CgroupDriver}} cgroupVersion={{.CgroupVersion}} rootless={{.SecurityOptions}} cpus={{.NCPU}} mem={{.MemTotal}}' || echo "docker info FAILED"
|
||||
docker info 2>&1 | grep -iE "rootless|warning" || echo "(no rootless/warning lines)"
|
||||
ls -l /dev/fuse 2>&1 || echo "(no /dev/fuse)"
|
||||
- name: "Install k3d"
|
||||
run: curl -sSfL https://raw.githubusercontent.com/k3d-io/k3d/main/install.sh | TAG="$K3D_VERSION" bash
|
||||
- name: "Create k3d cluster"
|
||||
run: k3d cluster create install-test --image "$K3S_IMAGE" --wait --timeout 180s
|
||||
run: k3d cluster create install-test --image "$K3S_IMAGE" --wait --timeout 180s --no-rollback
|
||||
- name: "PROBE k3s did not come up (throwaway branch only)"
|
||||
if: failure()
|
||||
run: |
|
||||
docker ps -a
|
||||
echo "=== k3s node log ==="
|
||||
docker logs k3d-install-test-server-0 2>&1 | tail -120 || true
|
||||
echo "=== docker info ==="
|
||||
docker info || true
|
||||
- name: "PROBE cluster is usable (throwaway branch only)"
|
||||
run: |
|
||||
kubectl get nodes -o wide
|
||||
kubectl get --raw='/readyz?verbose' | tail -5
|
||||
kubectl -n kube-system get pods
|
||||
# Every chart reaching this step is one the exclusion filter let through,
|
||||
# so the script's SKIP branch is never taken here - it exists for local
|
||||
# runs. The variables below are empty for every chart but the one that
|
||||
|
||||
Reference in new issue
Block a user