Skip to content

chore: drop the NEXTEST_NO_INPUT_HANDLER workaround#3482

Open
max-sixty wants to merge 4 commits into
mainfrom
test-guidance
Open

chore: drop the NEXTEST_NO_INPUT_HANDLER workaround#3482
max-sixty wants to merge 4 commits into
mainfrom
test-guidance

Conversation

@max-sixty

Copy link
Copy Markdown
Owner

nextest#2878 (the run suspending with SIGTTOU when a test spawns an interactive shell, as the shell-integration-tests feature does) was fixed in nextest 0.9.118, so the NEXTEST_NO_INPUT_HANDLER=1 workaround threaded through the insta hook, CI, and the test docs is obsolete. Verified on nextest 0.9.132: the shell-wrapper tests run to completion under a real PTY without the variable.

.config/nextest.toml now pins nextest-version = "0.9.118", so an older nextest fails with a clear version error instead of suspending mid-run.

This was written by Claude Code on behalf of max

max-sixty and others added 4 commits July 13, 2026 16:26
CLAUDE.md told every session to run the full pre-merge gate (full nextest
suite + lints + doctests + rustdoc) before each commit, which is redundant
with the gate wt merge runs itself and with CI's required full matrix.
Describe what the commands do and when they run automatically; leave the
decision of what to run during iteration to the session.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
# Conflicts:
#	CLAUDE.md
nextest#2878 (SIGTTOU suspension when a test spawns an interactive
shell) was fixed in nextest 0.9.118; pin that as the required floor in
.config/nextest.toml instead of threading the env var through the insta
hook, CI, and docs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

2 participants