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 3fe7a97
Browse filesBrowse the repository at this point in the historyBrowse files
Keep the job-control test's terminal setup out of bash's way
Two intermittent failures of test_pipeline_stops_with_cmd2_and_returns_terminal
under parallel load, neither caused by cmd2:
- Interactive bash intermittently stops a job it has just started on a
TOSTOP terminal, before the job runs any code of its own. The test set
TOSTOP before starting bash in its exit_sigint cases, so the launch of
the application, or of printf or stty during a stop, was sometimes
reported Stopped. Reproduced without cmd2: across 14 parallel bash
sessions launching Python, 10 of 2,240 launches stopped with TOSTOP set
and none of 2,240 without it. The test now sets TOSTOP only once the
pager owns the terminal, and again after fg: while the job is stopped,
bash restores its own terminal modes, so its commands run without it.
TOSTOP is still in effect when Ctrl-C is sent, which is what the test
needs it for.
- The pseudo-terminal occasionally reported its old size after the test
resized it while the job was stopped, though every process of the job
was stopped and nothing else sets a size. The test now confirms the new
size through the shell and resizes again if the shell saw the old one,
reporting every attempt if it never takes.
0 commit comments