diff options
| author | David Balatero <dbalatero@gmail.com> | 2026-05-05 11:45:41 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-05-05 11:45:41 -0400 |
| commit | 78111e5371f50f42d3999b2e475953d9c8a30c27 (patch) | |
| tree | 919b83d2db557b6c879c1e600132161cf0d6b45b /runtime/lua/vim/provider/python.lua | |
| parent | 10b739aac1e27f83ef98a70961ca5fe7c0079264 (diff) | |
| download | rneovim-78111e5371f50f42d3999b2e475953d9c8a30c27.tar.gz rneovim-78111e5371f50f42d3999b2e475953d9c8a30c27.tar.bz2 rneovim-78111e5371f50f42d3999b2e475953d9c8a30c27.zip | |
test: flaky terminal channel exitcode check #39580
Problem:
The `nvim_get_chan_info()` terminal channel test used `shell-test INTERACT` to verify that `jobstop()` reports an unhandled `SIGHUP` as exit code `129`.
`INTERACT` reads from stdin with `fgets()`, so closing the PTY could race with `SIGHUP` delivery. If `fgets()` observed EOF first, `shell-test` exited normally with code `0`, causing intermittent failures on slower sanitizer builds.
Solution:
Add a `shell-test HOLD` mode that prints a readiness prompt and then waits without reading stdin. Use it for the `SIGHUP` assertion so PTY EOF cannot make the helper exit normally before the signal path is observed.
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions