fix(test): raise input.test.ts pipeline timeouts to 30s#1176
Merged
Conversation
…1170) The `pipeline input` describe block in `apps/cli/test/commands/eval/pipeline/input.test.ts` exhibits the same 5s-default timeout flake under suite contention as the e2e test fixed in #1170. Each test spawns a `bun apps/cli/src/cli.ts pipeline input ...` subprocess that completes in ~1-2s in isolation but routinely overshoots 5s under `bun --filter agentv test` contention. Apply the same per-test timeout bump (`it(name, fn, 30_000)`) to all 10 tests in the describe block. The user brief named three sibling tests (`writes code_graders/<name>.json for deterministic assertions`, `omits experiment from manifest...`, `falls back to eval file basename...`); the remaining seven exhibited identical SIGTERM-at-5s failures in the same suite run, so the bump is applied uniformly to prevent partial coverage churn. Same one-line treatment per the #1170 precedent.
Deploying agentv with
|
| Latest commit: |
3afcd68
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://255cb884.agentv.pages.dev |
| Branch Preview URL: | https://fix-input-test-pipeline-time.agentv.pages.dev |
This was referenced Apr 27, 2026
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.
Follow-up to #1170. Same 5s-default timeout flake observed in the
pipeline inputdescribe block inapps/cli/test/commands/eval/pipeline/input.test.tsduring repeatedbun --filter agentv testruns after the #1166/#1167/#1168 land.Each test in the block spawns a
bun apps/cli/src/cli.ts pipeline input ...subprocess that completes in ~1-2s in isolation but routinely overshoots 5s under suite contention.The user brief named three sibling tests (
writes code_graders/<name>.json for deterministic assertions,omits experiment from manifest...,falls back to eval file basename...); the remaining seven exhibited identical SIGTERM-at-5s failures in the same suite run, so the per-test bump is applied uniformly to all 10 tests in the block to prevent partial-coverage churn.Same one-line treatment per the #1170 precedent (
it(name, fn, 30_000)— Bun test's numeric third-arg form).Test plan
bun test apps/cli/test/commands/eval/pipeline/input.test.ts— passes (10/10)bun --filter agentv test— nopipeline input >failures (verified across 3 consecutive suite runs)