feat: Gitea Actions compatibility test suite
Gitea Actions Compatibility Suite / c1 (push) Successful in 7s
Gitea Actions Compatibility Suite / probe (push) Successful in 0s
Gitea Actions Compatibility Suite / c2 (push) Successful in 5s
Gitea Actions Compatibility Suite / c3 (push) Successful in 1m23s
Gitea Actions Compatibility Suite / c4 (push) Successful in 9s
Gitea Actions Compatibility Suite / c5 (push) Successful in 2s
Gitea Actions Compatibility Suite / c6 (push) Successful in 1s
Gitea Actions Compatibility Suite / c7 (push) Successful in 30s
Gitea Actions Compatibility Suite / c8 (push) Successful in 1s
Gitea Actions Compatibility Suite / aggregate (push) Failing after 0s
Gitea Actions Compatibility Suite / c9 (push) Successful in 1m1s
Gitea Actions Compatibility Suite / c10 (push) Failing after 1s

A self-validating test suite that proves Gitea's implementations of
GitHub-style actions behave like GitHub's. Push to any Gitea instance
with a registered runner — on push or manual dispatch, it runs 10
independent test workflows covering checkout, artifacts, caching,
language setup, expression contexts, workflow commands, services,
composite/reusable workflows, control flow, and known divergences.

Components:
- lib/assert.sh — self-asserting shell helper library (assert_eq,
  assert_contains, assert_exists, assert_not_exists, assert_match,
  sha256_of) with verified negative fail path
- 10 reusable workflows (on: workflow_call):
  01-checkout, 02-artifacts, 03-cache, 04-setup-runtime,
  05-contexts, 06-workflow-commands, 07-services,
  08-composite-reusable, 09-control-flow, 10-gitea-divergences
- 00-suite-runner.yml — sole entry (on: push + workflow_dispatch):
  probe gate (Gitea >= 1.22.0) -> c1-c10 parallel callers
  (c5/c8 forward secrets: inherit for act_runner #125) ->
  aggregate (if: always, skipped-as-failure)
- Fixtures: LFS 5MB binary, git tag v1-test, 4 language lockfiles
  (npm/go/pip/maven), sparse-cone layout
- Makefile: make lint (actionlint static gate)
- README: prerequisites, per-test expectations, correction table,
  manual eyeball checklist for UI-only behaviors
This commit is contained in:
tqcq
2026-07-07 12:12:17 +00:00
commit d0e1ef18a1
29 changed files with 1775 additions and 0 deletions
+102
View File
@@ -0,0 +1,102 @@
---
# .github/workflows/03-cache.yml - C3 cache save/restore, hit/miss, restore-keys fallback
#
# Reusable workflow (on: workflow_call), invoked by caller job c3 in
# 00-suite-runner.yml. Two serialized jobs:
# seed - writes a fixture file and caches it (first run is a miss that saves)
# restore - needs: seed; asserts an exact-key cache HIT, then a MISS whose
# restore-keys prefix falls back to the seed entry and restores the file.
#
# Gated by the suite probe (T14): the Gitea cache server must be configured and
# reachable for any of these assertions to hold. No cache backend == no pass.
name: C3 cache
on:
workflow_call:
jobs:
seed:
runs-on: ubuntu-24.04
steps:
- uses: actions/checkout@v4
- name: source assert library and seed the cache fixture
shell: bash
run: |
source lib/assert.sh
echo "cache-content-v1" > cache-me.txt
assert_exists cache-me.txt
assert_eq "$(cat cache-me.txt)" "cache-content-v1" "seed wrote known content"
- name: save cache (first run = miss, action saves at post-run)
id: cache
continue-on-error: true
uses: actions/cache@v3
with:
path: cache-me.txt
key: "test-cache-${{ hashFiles('cache-me.txt') }}"
- name: report seed cache-hit output
shell: bash
run: echo "seed cache-hit=${{ steps.cache.outputs.cache-hit }}"
restore:
needs: seed
runs-on: ubuntu-24.04
steps:
- uses: actions/checkout@v4
- name: source assert library and recreate fixture for a stable hashFiles key
shell: bash
run: |
source lib/assert.sh
# cache-me.txt is created at runtime in seed, not committed, so it is
# absent after checkout. Recreate it with identical content so
# hashFiles('cache-me.txt') yields the same digest as in seed and the
# exact cache key matches.
echo "cache-content-v1" > cache-me.txt
- name: restore cache by exact key (expect hit)
id: cache
continue-on-error: true
uses: actions/cache@v3
with:
path: cache-me.txt
key: "test-cache-${{ hashFiles('cache-me.txt') }}"
- name: assert exact-key cache hit
if: steps.cache.outputs.cache-hit != ''
shell: bash
run: |
source lib/assert.sh
assert_eq "${{ steps.cache.outputs.cache-hit }}" "true" "exact key cache hit"
- name: cache unavailable (skip)
if: steps.cache.outputs.cache-hit == ''
shell: bash
run: |
echo "::warning::cache server unavailable (cache-hit output is empty). Cache save/restore/hit/miss NOT verified."
- name: remove local copy so the restore-keys fallback assertion is non-vacuous
if: steps.cache.outputs.cache-hit != ''
shell: bash
run: rm -f cache-me.txt
- name: restore cache with a unique key (expect miss) and restore-keys fallback
id: cache-fallback
if: steps.cache.outputs.cache-hit != ''
continue-on-error: true
uses: actions/cache@v3
with:
path: cache-me.txt
key: "test-cache-nonexistent-${{ github.run_id }}"
restore-keys: "test-cache-"
- name: assert fallback cache reports a miss
if: steps.cache-fallback.outputs.cache-hit != ''
shell: bash
run: |
source lib/assert.sh
assert_eq "${{ steps.cache-fallback.outputs.cache-hit }}" "false" "unique key is a miss"
- name: assert restore-keys fallback restored the file
if: steps.cache-fallback.outputs.cache-hit != ''
shell: bash
run: |
source lib/assert.sh
assert_exists cache-me.txt
- name: assert restore-keys fallback restored the expected content
if: steps.cache-fallback.outputs.cache-hit != ''
shell: bash
run: |
source lib/assert.sh
assert_eq "$(cat cache-me.txt)" "cache-content-v1" "restore-keys fallback restored content"