Repository navigation
test/ci: CI and test-suite health sweep (ssw.2-4, 6nh.1, 6nh.3, nm2.4) - #5
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…g-cli-6nh.1) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…li-6nh.3) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…m2.4) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…est_command (log-cli-ssw.4) turbo's test task already dependsOn build, so CI was build-before-test. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…li-ssw.3) Flake baseline: 10 consecutive bun test runs against a freshly built dist/cli.js, 108/108 pass each. The two elapsedMs bounds guard against the 5000ms summary fallback, so 3000ms keeps that signal. The 120ms URL gap and 0.06s command sleep are input timing, not assertions: runSummary only finishes once every source reports done, so they cannot race the 150ms quiet window. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
… (log-cli-ssw.1) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
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.
Batch A of the backlog sweep: CI and test-suite health, plus coverage.
tests/fixtures.test.tsguards theexamples/*.logentry-count contract (mixed.log 5 = 3 json + 2 text; mixed-2.log 3 = 2 json + 1 text). The fixtures themselves landed in 8165602.bun testruns against a freshly builtdist/cli.jsall passed (108/108 each). The twoelapsedMs < 1500bounds are now< 3000, which still catches a fallback to the 5000ms summary timeout. Commit message has the reasoning for the other timing points.bun-version: 1.4.2(same aspackageManager) in ci/release-cli/version workflows. Setsknowledge-base/config.ymltest_commandtobun run build && bun test && tsc --noEmit. CI already ran build before test, because turbo'stesttaskdependsOn: ["build"].tests/pathValue.test.tscovers all parsePath throw paths, thefound:falseshort-circuit, and.[]==[].readTerminalSizehelper fromuseTerminalSizeand tests it. Runtime behavior is unchanged.tests/cmdSource.test.tsdocuments that stdout and stderr are both captured, with source tagging and thestderr |prefix.ssw.4's acceptance asks for 3 consecutive green CI runs on this PR. That check is still open.
Revert plan if main goes red after merge:
git revert <merge-commit>, or revert only the workflow commit (ci: pin bun 1.4.2 ...).Local: typecheck clean, lint 0 errors, 108/108 tests, build OK.
🤖 Generated with Claude Code