test: dev CI baseline probe (empty commit) — close after it reports #90
Closed
tim.lingo
wants to merge 1 commits from
test/dev-ci-baseline into dev
pull from: test/dev-ci-baseline
merge into: :dev
:main
:docs/operator-naming-convention
:stage-elp-native-lang
:stage-elp-lang-consolidation
:stage-elp-es-port
:engram-tiered-storage
:dev
:engram-persistence-integrity
:feat/engram-reseed-route
:feat/el-route-decorators
:test/dev-ci-baseline
:fix/cgi-identity-emission-clean
:fix/cgi-identity-emission
:feat/AddingReadme
:stage
:reconcile/el-cluster-windows-runtime
:fix/durable-response-truncation
:fix/engram-lexical-tokenized-search
:fix/http-fs-read-len
:hotfix/ci-stage-main-publish-hardening
:hotfix/ci-dev-publish-hardening
:hotfix/stage-elc-engram-integration
:feat/ranked-engram-search
:hotfix/win-runtime-portability
:hotfix/runtime-engram-get-node-by-label
:feat/engram-semantic-search
:hotfix/elc-fixes
:hotfix/el-runtime-leak-and-persist
:integrate/local-main-commits
:fix/runtime-load-merge-2026-06-30
:fix/windows-rusage-guard
:fix/http-response-truncation
:salvage/tim-wip-presync-20260625
:feat/windows-el-runtime
:feat/accumulation-layer
:fix/runtime-integrity-reconcile
:fix/engram-save-atomic-darwin
:chore/live-darwin-runtime
:feat/wm-api-and-http-serve-async
:fix/engram-node-full-field-corruption
:fix/llm-model-and-utf8
:fix/elb-monolithic-link
:fix/ci-gcloud-install-order
:fix/native-test-precompile-runtime
:fix/ci-base-dev-first-run
:fix/elc-parser-elb-build
:fix/elc-oom-checkout
:fix/css-str-join-separator
:fix/html-template-if-style-script
:fix/elb-gcc-bracket-depth
:fix/ci-openssl-linker
:feat/ci-hook-test
:feat/native-testing
:runtime/integrate
:fix/http-serve-1-arg-compat
:feat/el-html-templates
:feat/js-browser-runtime
1 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
ac248887c2 |
test: empty commit — is dev CI red independent of any change?
El SDK CI - dev / build-and-test (pull_request) Failing after 12m14s
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> |