It looks like there’s a race condition—actually, I think I’m abusing this term—that occurs when the handin server runs out of memory while (re-)evaluating a checker module. Specifically, it appears that following such a failure, subsequent attempts to check this assignment simply enter a stalled state and eventually report server timeouts. My initial guess would be that there’s a “I’m waiting for this module to finish compiling” flag that gets set and then not unwound by the OOM, and subsequent attempts see that the flag is set and just wait for the (now halted) compilation/evaluation to finish.
I haven’t yet dived into the handin-server code because I’m hoping that someone will tell me that this is a known problem or something with an easy fix :). John -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
