19:39:44|3b|more windows test results, lots of stuff i don't recognize from last time i ran tests :/ https://gist.github.com/3b/714825e148ff605250cadac22fb57586
19:40:15|3b|though pathname stuff might just be intended changes without changing tests to match
19:49:29stassatssetfilepointerex just hangs on stdin
20:23:31stassatslooks like two non-nested whens got into a cond
20:28:07stassatsi think there's been enough fixes for windows (not just for regressions) that i might have enough extra motivation to post up a binary come release time
20:31:11|3b|ACTION wonders if the test hangs on windows got more deterministic at some point
20:32:49|3b|(or the non-deterministic hangs went away and were replaced by deterministic ones)
20:35:20|3b|fairly small sample set so far, but threads.impure.lisp hangs on :all-threads-have-abort-restart. if i comment that out it hangs on (:condition-variable :notify-multiple). comment both and it finishes
20:35:57|3b|and now that i typed all that out it seems to have hung somewhere else on the 5th or 6th try :p
20:47:10stassats`|3b|: interrupts are particularly bad
20:47:18stassats`i've even seen the code that does interrupts, there's no intention for it to be right
20:49:26|3b|all-threads-have-abort-restart seems to be locking in the test harness rather than the test itself
20:49:41stassats`the only solution to windows woes i can envision: replacing safepoints with good old signals, or whatever is the equivalent on windows
20:49:58|3b|runs OK by itself and lookss like it exits the loop when run inside with-test
20:50:15stassats`although safepoints is a good idea in theory, it's not implemented right, at least wrt interrupts
20:59:07|3b|possibly some race with thread termination when with-tests tries to terminate it again if it isn't dead after the first time?
20:59:44|3b|assuming that is even a reasonable thing to do in the first place, which i'm not sure about (or i could be misreading the code instead)