-
Notifications
You must be signed in to change notification settings - Fork 4
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
[cogserver] ShellUTest fails (Create rep 29 of 30 in thread N failed) #46
Comments
😞 I don't beleive that changes to the atomspace should have affected this test. This implies that there's some race condition somewhere, and that boost-1.62 hides it better than 1.67 |
This test no longer fails, it takes around 200 seconds and throws this guile error but completes:
Full output
|
I think the spewing output is normal. The test starts an inf-loop of scheme code in the "foreground" thread, and then intentionally sends a ctrl-C over the telnet shell, with the idea that this should kill the inf-loop. What actually happens is that the thread handling the socket, when it receives the magic byte sequence for ^C, then sens a guile interrupt to the "foreground" thread, which will result in some kind of unhappy complaint w/ stack trace from the interrupted thread. The exception is caught, the complaint is serialized to string and sent via socket back to the user, who gets to read it. |
Oh, and if I recall correctly, the test is designed to run exactly 180 seconds... Its starting dozens of network connections to the server, splatting stuff across each connection, checking to see if the server gets tangled up in handling all this. Three minutes should be enough to expose race conditions, if they exist. |
Oh, and final remark: once every few dozen(???) runs, the test fails, just as its finishing. There's a short read somewhere; the test harness is still sending data even as the server is shutting down after 3 minutes. Normally, it all terminates correctly, but sometimes not. |
After updating
atomspace
ShellUTest
test fails with many outputs like this just with different thread number:I'm using boost162 like suggested in #40 comment, and have also tried with boost 166 but got the same error.
The text was updated successfully, but these errors were encountered: