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
FWIW, I just got the test failure below (on Arch Linux):
#### Regression-testing /home/johno/GitRepos/KornShell/ksh/arch/linux.i386-64/bin/ksh ####
test pty begins at 2023-06-08+08:18:03
test pty passed at 2023-06-08+08:18:42 [ 59 tests 0 errors ]
test pty(C.UTF-8) begins at 2023-06-08+08:18:42
pty.sh[111]: FAIL: POSIX sh 026(C): line 127: expected "(Stopped|Suspended)", got EOF
test pty(C.UTF-8) failed at 2023-06-08+08:19:23 with exit code 1 [ 59 tests 1 error ]
Total errors: 1
CPU time user: system:
main: 0m00.003s 0m00.003s
tests: 0m00.590s 0m00.202s
I can only get this to happen while the CPU usage on all cores is around 100% during a heavy workload.
The text was updated successfully, but these errors were encountered:
I have seen this before on various systems, especially slow ones, or Linux with musl libc.
There seems to be a race condition in job notifications (like Stopped or Suspended) that causes them to not always be printed before the next prompt as expected. Pressing return to get another prompt will cause them to be printed in that case.
I can reproduce this quite easily on Alpine Linux arm64 (which uses musl libc):
Originally posted by @JohnoKing in #653 (comment)
FWIW, I just got the test failure below (on Arch Linux):
I can only get this to happen while the CPU usage on all cores is around 100% during a heavy workload.
The text was updated successfully, but these errors were encountered: