ci(ts): split the ts job into fast/slow lanes (like java)#170
Merged
Conversation
Mirrors the java-fast/java-slow split. The ts job ran build+typecheck + conformance + completeness + docker integration all in one job, so a docker/sidecar hiccup (or the integration flakiness fixed in #167) failed the whole ts signal and the fast correctness verdict waited on the slow integration. Now two parallel jobs: - ts-fast: build+typecheck, conformance, completeness — the pure-code signal, no docker/sidecar. - ts-slow: build + docker/sidecar integration tests (with the shared PG sidecar). ci-local.sh grows `--only ts-fast|ts-slow` (+ a build-only gate_ts_build for the isolated slow lane, since the workspace dist/ is needed for integration and the fast lane's build already produces it in the umbrella case). `--only ts` and a plain local run still run both lanes, byte-equivalent to before — no double build. detect still emits the umbrella token `ts`; both jobs gate on it. Verified: `--only ts-slow` builds and runs the full integration suite 116/0 green against a real sidecar; the dry-run lister confirms ts-fast/ts-slow/ts/no-flags all select the right steps with no duplicate build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ew1XfYSbEAezxjs9opynAe
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mirrors the java-fast/java-slow split (#162). The ts job ran build+typecheck + conformance + completeness + docker integration all in one job, so a docker/sidecar hiccup (or integration flakiness) failed the whole ts signal, and the fast correctness verdict waited on the slow integration.
Now two parallel jobs:
ci-local.shgrows--only ts-fast|ts-slowplus a build-onlygate_ts_buildfor the isolated slow lane (the workspacedist/is needed for integration; the fast lane's build already produces it in the umbrella case, so no double build).--only tsand a plain local run still run both lanes, byte-equivalent to before.detectstill emits the umbrellats; both jobs gate on it.Verified:
--only ts-slowbuilds and runs the full integration suite 116/0 green against a real sidecar; the dry-run lister confirmsts-fast/ts-slow/ts/no-flags select the right steps with no duplicate build. Validated end-to-end via aworkflow_dispatchrun on this branch before merge.🤖 Generated with Claude Code