The racketcs-asan failure continues, but I have no idea what’s going on. I’m inclined to disable that CI job until someone can replicate it.

The current state of our CI failures: 1. I think I’ve fixed DrDr. 2. The Linux 3m tests are timing out consistently. The version labeled “test–3m (nocify, jit, efp, clang) ” times out in the future tests: https://github.com/racket/racket/runs/3165512173?check_suite_focus=true#step:24:6 The other version, using cify and nojit, times out in package installation (after 6 hours, so something is hung): https://github.com/racket/racket/runs/3165512205?check_suite_focus=true#step:9:386 3. The Linux ubsan tests also timeout, in testing: https://github.com/racket/racket/runs/3165423785?check_suite_focus=true 4. The snapshot generation tests seem to have an s3-sync failure: https://github.com/racket/racket/runs/3162283736?check_suite_focus=true#step:7:9 5. It looks like the ASan problem just went away on its own. As far as I can tell, none of these failures reproduce anywhere else.