<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 20 Feb 2018, at 13:07, Robert Goldman wrote:</p>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
<p dir="auto">On 20 Feb 2018, at 10:49, Faré wrote:</p>
<blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999">
<p dir="auto">I don't know what the root cause is here, but this looks like the same<br>
bug that is supposed to be fixed, and the fix works for me. Does<br>
Jenkins use some fancy filesystem setup that confuses the timestamp<br>
checking?</p>
</blockquote>
<p dir="auto">It might. Jenkins does everything in a workspace, which is similar to a home directory, but isn't one.</p>
<p dir="auto">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.</p>
<p dir="auto">So I'm still puzzled.</p>
<p dir="auto">R</p>
</blockquote>
<p dir="auto">My latest test on Jenkins did <em>not</em> 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.</p>
<p dir="auto">R</p>
</div>
</div>
</body>
</html>