ci: retrigger marker — rerun ci.yml for fe79810 (Build log was never persisted)
CI / Architecture Guardrails (push) Successful in 2m10s
CI / Typecheck (push) Successful in 3m51s
CI / Lint (push) Successful in 3m51s
CI / Assistant Split Regression (push) Successful in 6m9s
CI / Unit Tests (push) Successful in 8m53s
CI / Build (push) Successful in 7m32s
CI / E2E Tests (push) Successful in 7m2s
CI / Fresh-Linux Docker Deploy (push) Successful in 8m11s
CI / Release Images (push) Successful in 6m15s
Nightly Security / Dependency Audit (push) Successful in 1m13s
CI / Architecture Guardrails (push) Successful in 2m10s
CI / Typecheck (push) Successful in 3m51s
CI / Lint (push) Successful in 3m51s
CI / Assistant Split Regression (push) Successful in 6m9s
CI / Unit Tests (push) Successful in 8m53s
CI / Build (push) Successful in 7m32s
CI / E2E Tests (push) Successful in 7m2s
CI / Fresh-Linux Docker Deploy (push) Successful in 8m11s
CI / Release Images (push) Successful in 6m15s
Nightly Security / Dependency Audit (push) Successful in 1m13s
Previous run's Build job failed but Gitea's actions log store didn't retain the output (dbfs reports the file missing), so we can't diagnose from here. Rerun to either reproduce the failure with a persisted log, or green-ify. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
name: CI
|
||||
|
||||
# Retrigger marker: b2d89ca (docker-deploy smoke retry)
|
||||
# Retrigger marker: fe79810 (Build log lost — retrigger to re-observe)
|
||||
on:
|
||||
push:
|
||||
branches: [main]
|
||||
|
||||
Reference in New Issue
Block a user