mirror of
https://github.com/hanzoai/forge.git
synced 2026-10-30 15:00:39 +00:00
These jobs asked for `hanzo-linux-amd64`. No runner advertises that label, so they never ran — and crucially they did not FAIL either. A job requesting an unadvertised label queues until the 24h timeout, which reads as "CI is slow" rather than "CI is misconfigured", so this hid rather than surfaced. Verified live against git.hanzo.ai /api/v1/admin/actions/runners rather than inferred: the four ONLINE runners (git-runner-0..3) advertise exactly ubuntu-latest, ubuntu-22.04, ubuntu-24.04 and hanzo-build-linux-amd64. The three self-hosted hosts that carry other labels (spark gb10/cuda, dbc m4max/metal, evo gfx1151/rocm) are all OFFLINE, and none of them advertises a linux-amd64 pool anyway. So there is exactly ONE usable pool today and this points at it. Fleet-wide this was 27 jobs across 14 files in 8 repos. The one remaining mention of the old label is a COMMENT in iam2/image.yml that documents this very defect — deliberately left intact.
38 lines
979 B
YAML
38 lines
979 B
YAML
name: e2e-tests
|
|
|
|
on:
|
|
pull_request:
|
|
|
|
concurrency:
|
|
group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
|
|
cancel-in-progress: true
|
|
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
files-changed:
|
|
uses: ./.hanzo/workflows/files-changed.yml
|
|
|
|
test-e2e:
|
|
if: needs.files-changed.outputs.backend == 'true' || needs.files-changed.outputs.frontend == 'true' || needs.files-changed.outputs.e2e == 'true'
|
|
needs: files-changed
|
|
runs-on: hanzo-build-linux-amd64
|
|
steps:
|
|
- uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7
|
|
- uses: ./.github/actions/go-setup
|
|
- uses: ./.github/actions/node-setup
|
|
- run: make deps-frontend
|
|
- run: make frontend
|
|
- run: make deps-backend
|
|
- run: make backend
|
|
env:
|
|
TAGS: bindata
|
|
- run: make playwright
|
|
- run: make test-e2e
|
|
timeout-minutes: 10
|
|
env:
|
|
TAGS: bindata
|
|
FORCE_COLOR: 1
|
|
GIT_TEST_E2E_DEBUG: 1
|