-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sporadic interactive test failures #330
Comments
Looks like terminal control characters at the end.
|
|
What platform are you on? I can't reproduce this |
I can reliably reproduce on OpenBSD-current, i386 (32 bit) and amd64 (64 bit). |
OK,thanks. I don't have openbsd available right now but when I do I'll try to reproduce |
While trying to reproduce this on an OpenBSD VM i notice that a fresh checkout of jimtcl fails to build because of that braindead linker output OpenBSD generates:
Re-running configure a second time works - it's only the extra output which confuses it. That was already resolved in upstream autosetup. |
fwiw this is reproducible on an OpenBSD 7.6 vm:
|
What version? Is this master (3a2cfdf). Should be fixed there. |
It was a freshly-cloned copy of [3a2cfdf]. It repros consistently here with:
|
Thanks. I'll hopefully be able to fire up an openbsd vm soon and reproduce this. |
OK, two separate issues here. The configure problem is because we don't have the redirection order correct in autosetup-find-tclsh The occasional test failures are do do with how linenoise waits for the window size response to be returned. It has some fixed timeouts that don't seem to work well on OpenBSD (at least in a VM). I'll have to investigate further to see how to make this more reliable. |
Because the child process is being controlled via pty pair, the window size is not available. Sometimes the first char is eaten by the code waiting for the window size response and then everything goes downhill from there. |
I've pushed some changes to branch openbsd-fix |
Thanks, that's quite a bit of work!
|
linenoise.c line 930
|
OK, I've made a couple of more fixes. Please let me know how it goes. |
Here's what I've got so far: 32bit machine: over 16000 test iterations without fail. I don't think those numbers are significant, just random. I'll do some more testing and report back. |
The interactive tests will fail sometimes.
This seems to have started with 8.2.
$ cd /path/to/jim/tests
$ while true; do jimsh interactive.test; done
The text was updated successfully, but these errors were encountered: