Probe which actions/cache variant can reach the v2 cache service
CI / Tests (PHP 8.1) (pull_request) Successful in 1m1s
CI / No Debug Code (pull_request) Successful in 2s
Cache Service Probe / Cache Service Probe (pull_request) Successful in 2s
Cache Service Probe / cache@v6 (pull_request) Successful in 3s
Cache Service Probe / cache@v4 + ACTIONS_CACHE_SERVICE_V2 (pull_request) Successful in 59s
Cache Service Probe / cache@v6 + ACTIONS_CACHE_SERVICE_V2 (pull_request) Successful in 1m7s
CI / Tests (PHP 8.2) (pull_request) Successful in 1m1s
CI / Coding Standards (pull_request) Successful in 4m47s
CI / Tests (PHP 8.3) (pull_request) Successful in 2m58s
CI / PHPStan (pull_request) Failing after 12m12s
CI / Build Plugin Zip (pull_request) Skipped

The first probe answered the original question and raised a better one.
ACTIONS_CACHE_URL is unset but ACTIONS_RESULTS_URL points at
gitea-unsupervised-git-http.gitea.svc.cluster.local:3000, so the runner
does serve a cache — the v2 service, not v1. actions/cache resolves to
v4.3.0, which can speak v2, but only when ACTIONS_CACHE_SERVICE_V2 is
set, and the runner does not set it. So the action falls back to v1,
finds no endpoint, and trips its GHES gate on the way past.

Three variants to find one that reaches the service that is already
running: v4 with the flag forced, v6.1.0 which is current, and v6 with
the flag. Any that saves is a fix that lives in this repository.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Uw545F1vveNJKjzLxdi2ks
This commit is contained in:
2026-08-20 15:16:25 -03:00
co-authored by Claude Opus 5
parent a26c481c8f
commit 3ec2440bd1
+38
View File
@@ -51,3 +51,41 @@ jobs:
run: |
echo "runner.arch = ${{ runner.arch }}"
echo "runner.os = ${{ runner.os }}"
# The first probe showed ACTIONS_CACHE_URL unset but ACTIONS_RESULTS_URL set,
# i.e. the runner serves the v2 cache service and not v1. actions/cache v4.3
# can speak v2, but only when ACTIONS_CACHE_SERVICE_V2 is set, and it is not.
# These three variants test the ways round that.
variant-v4-flag:
name: cache@v4 + ACTIONS_CACHE_SERVICE_V2
runs-on: ubuntu-latest
env:
ACTIONS_CACHE_SERVICE_V2: "true"
steps:
- run: mkdir -p /tmp/probe && head -c 1048576 /dev/urandom > /tmp/probe/blob
- uses: actions/cache@v4
with:
path: /tmp/probe
key: probe-v4flag-${{ github.run_id }}
variant-v6:
name: cache@v6
runs-on: ubuntu-latest
steps:
- run: mkdir -p /tmp/probe && head -c 1048576 /dev/urandom > /tmp/probe/blob
- uses: actions/cache@v6
with:
path: /tmp/probe
key: probe-v6-${{ github.run_id }}
variant-v6-flag:
name: cache@v6 + ACTIONS_CACHE_SERVICE_V2
runs-on: ubuntu-latest
env:
ACTIONS_CACHE_SERVICE_V2: "true"
steps:
- run: mkdir -p /tmp/probe && head -c 1048576 /dev/urandom > /tmp/probe/blob
- uses: actions/cache@v6
with:
path: /tmp/probe
key: probe-v6flag-${{ github.run_id }}