On Sat, Oct 19, 2013 at 5:33 PM, Dave Cooper david.cooper@genworks.comwrote:
Ok here's a patch for that.
It seems to fix things for allegro/Windows, but now it reared its head again on sbcl/Windows.
Welp, it just happened again on alisp -- and that was in a clean build/ directory before any other tests had run (alisp was the first in the list).
I'm pretty sure these test-stamp-propagation failures are only happening on Windows now.
More curious than ever now about how we think we're doing "touch" on Windows...