I committed a variant of your patch. See 3.0.2.30. Can you send a failure log? Touch is not part of Windows, but it's probably part of either cygwin or msys or whichever add-on you run the test scripts with. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Yield to temptation; it may never pass your way again. — Robert Heinlein, "Time Enough For Love" On Sat, Oct 19, 2013 at 5:39 PM, Dave Cooper <david.cooper@genworks.com> wrote:
On Sat, Oct 19, 2013 at 5:33 PM, Dave Cooper <david.cooper@genworks.com> wrote:
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...