Repository navigation
[WRONG BRANCH] test: isolate provider fixture DNS and bound child lifetime - #1
Closed
Hylouis233 wants to merge 1 commit into
Closed
Hylouis233 wants to merge 1 commit into
Hylouis233 wants to merge 1 commit into
Conversation
Forward-port the test-only residue from 90eb461 onto current upstream dev. Keep real destination-policy and loopback HTTP transport, and retain every existing transport assertion plus the 15-second case deadline. Install a child-local DNS failure for the four fixture hostnames and assert all lookups. Bound the fixture child at 12 seconds with SIGKILL and retain upstream's existing awaited cleanup. Controlled delayed-DNS and hung-child comparisons reproduce the current failure and confirm the scoped fix on Linux.
|
✅ Deterministic PR hygiene checks passed. |
⏳ DRAFT
What to do
Its title has been prefixed with |
7 tasks done
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.
Summary
Verification
Linux, project-pinned Bun 1.4.0; dependency lock preserved, install scripts disabled, test environment stripped of provider credentials, fresh isolated homes, and loopback/mocked transports only.
bun test --isolate --parallel=1 ./tests/providers/provider-outbound.test.ts: 39 passed, 203 assertions.bun test --isolate --parallel=1 ./tests/routing/destination-policy-resolved.test.ts ./tests/lib/pinned-http.test.ts ./tests/lib/pinned-http-content-coding.test.ts ./tests/server/proxy-env.test.ts ./tests/lib/provider-egress.test.ts ./tests/providers/provider-egress-outbound.test.ts ./tests/test-layout.test.ts ./tests/test-layout-tooling.test.ts ./tests/ci-workflows/file-size-ratchet.test.ts: 174 passed, 1 Windows-only skip, 996 assertions.node node_modules/typescript/bin/tsc --noEmit: passed, using the frozen-lockfile TypeScript version.bun scripts/privacy-scan.ts: passed.git diff --check: passed. The exact tested tree is 74e81e00396c43b0c8767f3be765b51d40f73d13.The full suite was not run locally: the repository-wide run was disproportionate for this two-file harness-only staging draft in a shared sandbox. The generic wrapper also tries to bootstrap unrelated GUI dependencies, so local focused tests use the direct runner with the repository's normal preload.
Exact-head Cross-platform CI run 37034498379 completed successfully for 7f7719e: all four Linux test shards, aggregate ci, gates, Docker smoke, storage/API checks and Ubuntu/Windows keyring smoke passed. React Doctor and PR hygiene also passed. Native Windows/macOS test shards were skipped by the existing CI scope rules; they remain unverified for this patch.
The separate enforce-target gate reports only the expected review-baseline branch-name mismatch. This draft deliberately preserves the two-file review diff; do not retarget it to stale fork dev or treat it as an integration PR.
Checklist