Skip to content

test(runtime): keep native HTTP probe at a stable path - #304

Merged
XXPermanentXX merged 1 commit into
mainfrom
fix/native-http-probe-path
Nov 5, 2026
Merged

XXPermanentXX merged 1 commit into
mainfrom
fix/native-http-probe-path

Conversation

@XXPermanentXX

Copy link
Copy Markdown
Collaborator

The compiled native HTTP probe previously received a new temporary pathname on every test run, preventing path-based executable approvals from being reused.

Write only the compiled executable to test/native-http-probe/probe (probe.exe on Windows) and create its parent directory before compilation. Keep temporary script cleanup, compilation/signing, runtime selection, and all HTTP assertions unchanged. The existing /test/ ignore rule covers the output.

Validation:

  • pnpm exec vp check: passed with two existing warnings.
  • Existing HTTP test file: 48/48 passed across Node, Bun, and compiled binary, using an isolated Bun 1.3.14 copy matching CI via the existing BAILIAN_TEST_BUN override.
  • After one manual executable approval, two consecutive launches and a separate rebuild/version smoke test passed; the full 48-test run rebuilt the same path again.
  • git diff --check: passed. The full repository suite was not rerun.

The installed Bun remains 1.3.12. Its existing macOS binary-signing failure is outside this change; the same compiled artifact also fails signing at the original temporary location.

Approval retention duration depends on the endpoint security policy and has not been verified over 14 days. Independent simultaneous invocations of this test in one checkout share the output path.

@XXPermanentXX
XXPermanentXX merged commit 2c29049 into main Nov 5, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant