On 20 Feb 2018, at 13:07, Robert Goldman wrote:

On 20 Feb 2018, at 10:49, Faré wrote:

I don't know what the root cause is here, but this looks like the same
bug that is supposed to be fixed, and the fix works for me. Does
Jenkins use some fancy filesystem setup that confuses the timestamp

It might. Jenkins does everything in a workspace, which is similar to a home directory, but isn't one.

What's odd is that I only see this issue with MKCL. So it would have to be something special about the Jenkins workspace that is visible to MKCL, but not to other lisps.

So I'm still puzzled.


My latest test on Jenkins did *not* fail. I'm not happy about this -- I suspect there's something uncontrolled about the behavior of the test -- but on the other hand, I don't believe that this transient failure is a reason to hold back a release.


Reply via email to