Repository navigation
issues: libc_children's tty_interrupt can stall at the nested shell's line - #1127
Merged
Merged
Conversation
… line The stall was first attributed to #1111's scheduler step 1, on one run of each side. It also reproduces on main, in 1 of 4 local QEMU runs, against 0 of 6 at step 1 alone, so it is recorded on its own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Japabu
marked this pull request as ready for review
November 1, 2026 01:47
This was referenced Nov 1, 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
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.
Records a defect on main. No code changes.
Problem
libc_children'stty_interruptprobe sometimes stalls at "the nested line held" on the 2-CPU QEMU x86-64 boot. It was first attributed to #1111's scheduler step 1, on one run of each side.Evidence
Local QEMU runs; the logs are in
pr-1111/r2/tty.24a538c88f5ae75f6b(#1111's step 1 on that main)dd9bf974d(#1111's head)signal_quit)It reproduces on main, so it is recorded on its own. Its cause is not established.
Checks
cargo run -- --ci hostat2cc98a5f3: 107 steps, all green, exit 0.🤖 Generated with Claude Code