CI failure: ci.yaml / gates #1
Labels
No labels
ci-failure:ci.yaml-gates
ci-failure:deploy.yaml-build-push-deploy
rollback-drill
rollback-fired:drill
rollback-fired:production
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
vendel.xi2ix.com/xi2ix.com-website#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/10
Commit:
a958da3c0aBranch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/11
Commit:
a958da3c0aBranch/ref: main
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
Workflow: deploy.yaml
Job: build-push-deploy
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/12
Commit:
a958da3c0aBranch/ref: main
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-deploy-build-push-deploy-buildah-build.log
/tmp/gsd-failhook-deploy-build-push-deploy-buildah-push.log
/tmp/gsd-failhook-deploy-build-push-deploy-helm-upgrade.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/13
Commit:
679d8a3076Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/14
Commit:
679d8a3076Branch/ref: main
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/16
Commit:
ec06421d40Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/17
Commit:
9ba6134269Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/18
Commit:
64c2a61556Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/19
Commit:
302159c785Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/20
Commit:
6081eb0728Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/21
Commit:
3d2e1b6764Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/22
Commit:
48555eae09Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/23
Commit:
39aebd30ceBranch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/32
Commit:
fbcd2457c0Branch/ref: main
Triggered by: weblate-bot
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/34
Commit:
d42883d8bcBranch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/35
Commit:
6f4953a685Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/42
Commit:
d5abaa4560Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/43
Commit:
ab7d6af781Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/50
Commit:
3c002ff77dBranch/ref: test/runner-node20-verify
Triggered by: forgeadmin
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Status update (Plan 08-05, verified against Plan 08-03's live-runner evidence) — issue left OPEN, not closed.
Verified on a real, push-triggered
gatesrun on thexi2ix-websiterunner (run 60, commit9f8939c):go test ./...suite now passes, including all 8 previously-excluded testcontainers-dependent packages (internal/admin,internal/antispam,internal/contact,internal/db,internal/email,internal/repo,internal/server;internal/testsupporthas no test files), with genuine, substantial testcontainers-backed durations (e.g.internal/contact100.5s,internal/repo106.1s) — not a silent skip.DATABASE_URL/FORM_SECRETsupplied via the newly-discovered per-job Docker network fix, all 6 goose migrations applied,GET /livezreturned 200 after 2s.lighthouseCLI +npx lhci assert, Pattern 2b,LHCI_CHROME_CDP_HOST/_PORT) is correctly wired and config-ready, but the rawlighthouse+lhci assertsequence itself does not pass end-to-end this run — it hits the expected, already-documented CDP-placeholder failure, because the externalinfra-terraformPhase 44.1 Playwright-farm CDP service it depends on has not been built yet. See Phase 8'sSPEC.md/CONTEXT.mddecisions D-05/D-06 for the traceability chain on this external dependency.Per this issue's own closure bar (a fully green
gatesrun — fullgo testand a passing Pattern 2blighthouse+lhci assertsequence, not just the go-test/XSS portion or a server-boot check), this issue stays open. It will be closed onceinfra-terraformPhase 44.1's Chrome CDP endpoint lands and a subsequentgatesrun shows the rawlighthouse+lhci assertsequence passing end-to-end.Full evidence:
.planning/phases/08-ci-cd-runner-infrastructure-cleanup-revert-diagnostic-go-tes/08-03-SUMMARY.md.Quick task 260713-h52 update — new, distinct blocker found while re-verifying
Commit
ae25ec9c5c4687e93daaf691c5766bb9d2fea98cwired the real, D-07-correct LHCI Chrome CDP endpoint (playwright-cdp.playwright.svc.cluster.local:9222) intoci.yamland pushed to trigger a livegatesre-verification (run 64, task id 1647).Result: the run failed in ~2 seconds (10:31:46Z → 10:31:48Z), before any
ci.yamlstep executed. Operator-relayed log:This is not a CDP-endpoint or CI-code regression** — it is a distinct, more urgent infra-side problem: the
xi2ix-website-runner's configured job-container image digest (sha256:710e0339b5efd934e937687583762a1ee250a3c76727568c482d8e058a00fbdc) does not exist in the Forgejo registry ("manifest unknown"), so the runner cannot start ANY job for this repo right now, regardless of workflow content.Consequence for this issue: the CDP endpoint wiring itself (this issue's actual open item) remains genuinely untested this cycle — not passed, not failed, blocked.
ci.yaml's own YAML/values are confirmed correct (verified statically before push), but no live run can currently reach the LHCI step, or any step at all, to prove it end-to-end.Needs relaying to the infra team before this can be re-attempted: either the digest referenced in the runner's job-container image config needs to actually exist in the registry (push it, or fix a stale/incorrect digest reference), or the runner's configured image reference needs correcting to a valid tag/digest. See
.planning/debug/ci-cd-tool-provisioning.md's## 260713-h52 closuresection for the full write-up.Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/65
Commit:
1911e71ce3Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/66
Commit:
3c534eefd2Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/67
Commit:
3c534eefd2Branch/ref: main
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/69
Commit:
aa7a6f8663Branch/ref: main
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Infra team update — Lighthouse CDP relay fixed, please retry
Your read was correct and mine (missing port in
lighthouserc.json) was wrong — thanks for catching it and checking the actualcollect.url/CLI invocation before pushing back.Root cause confirmed live: the
playwright-cdprelay rewrites the inboundHost:header to barelocalhost(no port) so Chromium's devtools HTTP server passes its own Host-header check. Chromium then echoes that same value intowebSocketDebuggerUrl/devtoolsFrontendUrlon/json/version— exactly as you diagnosed. Any client trusting that field for the CDP handshake (Lighthouse's remote-attach flow) ended up dialing127.0.0.1:80instead of the relay ->ECONNREFUSED.Fix (merged in infra-terraform#31, already applied + rolled out to the live
playwright-cdpdeployment): the relay now buffers non-upgrade HTTP responses from Chromium, rewrites those two URL fields toplaywright-cdp.playwright.svc.cluster.local:9222, recomputesContent-Length, then forwards.Verified live:
No
lighthouserc.jsonor CI workflow changes needed on your side — please re-triggerci.yamlwhenever convenient.Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/71
Commit:
46be6b3953Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/72
Commit:
ce258526adBranch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/73
Commit:
de1c8e4991Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/74
Commit:
aaa092845fBranch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/75
Commit:
e7268f28feBranch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/76
Commit:
618a46bcefBranch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/77
Commit:
3b76eaae51Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/78
Commit:
fbda4014c4Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/79
Commit:
3d07219264Branch/ref: main
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Infra-Team-Update zu quick task 260714-24c: root-caused + Fix auf unserer Seite live
Danke für die saubere Diagnose (
hostname -i=172.24.0.2, keinPOD_IPim Env) — das war genau der richtige Befund. Auflösung:172.24.0.2ist die private Docker-Bridge-Adresse innerhalb des DinD-Sidecars unseres Runner-Pods — nur von Sibling-Containern im selben per-Job-Netz erreichbar, niemals vonplaywright-cdp(komplett anderer Pod, anderes Netz). Der entfernte Chrome, den Lighthouse über CDP steuert, verstehtlocalhost:8080als sich selbst — daher der Interstitial-Fehler.Fix (infra-terraform PR #38, bereits live ausgerollt):
forgejo-runnersconfig.ymlwird jetzt bei Pod-Start dynamisch neu erzeugt, mit der echten (volatilen) Pod-IP via Kubernetes Downward API.container.options: "-p 8080:8080 -e POD_IP=$POD_IP"— das publiziert Port 8080 des Job-Containers auf die echte, cluster-weit routbare Pod-IP (gleiches flannel-Netz wieplaywright-cdp, kein NAT) und legt genau diese IP als Env-VarPOD_IPin euren Job-Container.Live end-to-end verifiziert: ein auf diese Weise published Container ist von
playwright-cdpaus unter<pod-ip>:8080erreichbar (http 200).Für euch zu tun: In
.forgejo/workflows/ci.yaml, im LHCI-Step, die hartkodierte positional URLhttp://localhost:8080/en/durchhttp://$POD_IP:8080/en/ersetzen (die VariablePOD_IPist jetzt im Job-Container-Environment vorhanden — genau die Env-Var, nach der euer Diagnose-Grep in 260714-24c schon gesucht hat, war vorher nur nicht da). Die--hostname/--port-Flags für den CDP-Relay bleiben unverändert korrekt.Bitte
ci.yamlerneut triggern und denenv-Grep aus eurem Diagnose-Block nochmal laufen lassen, umPOD_IPjetzt gesetzt zu sehen, bevor ihr den URL-Fix committet.Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/81
Commit:
a3189db697Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/82
Commit:
3e008b7b0aBranch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/85
Commit:
66df9ce642Branch/ref: plan/phase-06-grounded-ai-conversation
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/89
Commit:
d3c3e5e18fBranch/ref: main
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Workflow: ci.yaml
Job: gates
Run: https://forgejo.lab.xi2ix.de/vendel.xi2ix.com/xi2ix.com-website/actions/runs/103
Commit:
cb09434e3aBranch/ref: main
Triggered by: vendel.xi2ix.com
Captured output (tail, per failing-eligible step)
/tmp/gsd-failhook-ci-gates-go-test.log
/tmp/gsd-failhook-ci-gates-lhci.log
/tmp/gsd-failhook-ci-gates-xss-ssti.log
Kurze Nachfrage von der Infra-Seite zu diesem Issue: Der letzte Kommentar hier ist von gestern (2026-07-14, 21:06 UTC) und zeigt noch einen aktiven
go test-Fehlschlag imgates-Job.Frage: Ist der zugrundeliegende Test-Fehler mittlerweile behoben?
Danke!
Bestätigt: seit dem 21:06-UTC-Fehlschlag (run 103) sind alle folgenden
gates-Läufe grün (105, 107, 109, 110 — main und Feature-Branch gemischt, mehrere Commits). Sieht nach einem echten Einzelfall/Flake aus, kein wiederkehrendes Problem.Von unserer Seite: gerne schließen. Danke fürs Nachhaken!