test: dev CI baseline probe (empty commit) — close after it reports #90

2026-08-09T19:46:00Z

tim.lingo commented

2026-08-09 19:46:00 +00:00

Not a change. An empty commit against dev, to answer one question the server will not answer any other way: IS DEV CI RED ON ITS OWN?

#89 reports red. This Gitea instance does not serve Actions logs (run-scoped route 404, job-scoped 500, web route 500), so the failure cannot be read.

Reproduced locally in the workflow's own image (ubuntu, linux/amd64, runner-image parity for libssl-dev):

control = dev head, no change
treatment = dev head + #89

Both self-host the compiler (gen2), both build elb, and both fail the SAME three timezone tests — earth-zone, dst-spring-forward, rhythm-grounding — with byte-identical test output. #89 changes nothing the workflow exercises.

If this empty commit is also red, dev CI is broken independent of any change and #89 is blocked by an unrelated failure. If it is green, the local reproduction is missing something and I keep digging.

Close either way; nothing here is meant to merge.

Not a change. An empty commit against dev, to answer one question the server will not answer any other way: IS DEV CI RED ON ITS OWN? #89 reports red. This Gitea instance does not serve Actions logs (run-scoped route 404, job-scoped 500, web route 500), so the failure cannot be read. Reproduced locally in the workflow's own image (ubuntu, linux/amd64, runner-image parity for libssl-dev): control = dev head, no change treatment = dev head + #89 Both self-host the compiler (gen2), both build elb, and both fail the SAME three timezone tests — earth-zone, dst-spring-forward, rhythm-grounding — with byte-identical test output. #89 changes nothing the workflow exercises. If this empty commit is also red, dev CI is broken independent of any change and #89 is blocked by an unrelated failure. If it is green, the local reproduction is missing something and I keep digging. Close either way; nothing here is meant to merge.

tim.lingo added 1 commit 2026-08-09 19:46:03 +00:00

test: empty commit — is dev CI red independent of any change?

El SDK CI - dev / build-and-test (pull_request) Failing after 12m14s

Details

ac248887c2

Baseline probe. #89 shows red on dev CI and this Gitea instance does not serve
Actions logs (404/500 on every route), so the only way to learn whether dev CI is
broken on its own is to run it against dev with no change at all.

Reproduced locally first: control (dev head) and treatment (dev + #89) produce
BYTE-IDENTICAL test results — both build the self-hosted compiler and elb, both
fail the same three timezone tests (earth-zone, dst-spring-forward,
rhythm-grounding). That exonerates #89 locally. This probe asks the same question
of the real runner.

Close once it reports.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

tim.lingo referenced this pull request

2026-08-09 20:00:15 +00:00

dev CI is red on an EMPTY commit — three timezone tests fail with no change present #91

tim.lingo closed this pull request

2026-08-09 20:00:33 +00:00

tim.lingo referenced this pull request

2026-08-09 20:01:01 +00:00

fix(codegen): emit the declared cgi identity — it was searched for in a list that cannot contain it #89