You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6772e5c
Browse filesBrowse the repository at this point in the historyBrowse files
test: stabilize interpreter subprocess fixtures (Fixes#557)
Use a stable shell with inline commands instead of executing freshly written files that can fail with ETXTBSY under concurrent tests. Preserve typed runner diagnostics and strengthen outcome assertions without changing production fallback behavior.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
For parser helpers, include malformed input, non-ASCII surrounding data, and case variations. For diagnostics, test pattern classification and expansion filtering separately. Keep temp paths unique with `tempfile` or process/counter-based names.
95
95
96
-
Before every Rust commit, run targeted tests and invoke the `rust-precommit` skill. Keep that skill as the single source of truth for required format and Clippy commands.
96
+
Before every Rust commit, run targeted tests and invoke the `rust-precommit` skill. Keep that skill as the single source of truth for required format and Clippy commands.
97
+
98
+
## Learnings
99
+
100
+
Do not execute freshly written scripts as concurrent Unix subprocess fixtures: spawning can fail with `ETXTBSY` (Text file busy). Prefer an existing interpreter such as `/bin/sh -c` with an inline script, or the existing test executable. Assert the typed runner outcome before checking an optional parsed result, so a spawn failure cannot masquerade as a successful negative parsing or timeout test.
0 commit comments