<div dir="ltr"><div><br></div>If you let me know what Jenkins happens to be then I may be able to give a look at the problem.<div>I have been planning an update to the latest ASDF for my upcoming (RSN) release of MKCL 1.1.11,</div><div>so I may as well squeeze that question in.</div><div><br></div><div>Regards,</div><div><br></div><div>JCB<br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 19, 2018 at 6:56 PM, Robert Goldman <span dir="ltr"><<a href="mailto:rpgoldman@sift.info" target="_blank">rpgoldman@sift.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">The failure isn't replicable to me, which bothers me some. I suspect it means that it's having side-effects in the file system that aren't entirely cleaned up. I'm eyeballing the test and it <em>does</em> affect the filesystem, and it does not remove the files (really symlinks) it creates. So ... potentially there could be insufficiently controlled side-effects that gave me a transient failure? I don't know. I suppose it's also possible that it does something with the filesystem that Jenkins isn't allowed to do, and that's why I got the Jenkins-only failure. But that explanation doesn't explain why I get failure only with Jenkins <em>and</em> MKCL.</p><div><div class="h5">
<p dir="auto">On 19 Feb 2018, at 16:43, Faré wrote:</p>
<blockquote style="border-left:2px solid #777;color:#777;margin:0 0 5px;padding-left:5px">
<p dir="auto">test-multiple works for me with asdf 3.3.1.4, mkcl 1.1.10.19-2dbfa99<br>
on Linux 4.14 x64.</p>
<p dir="auto">This is all long gone from my mental cache. The test could be better<br>
commented, but I suppose the purpose can be extracted by looking at<br>
its history then looking at related commits, bugs, bug fix commits,<br>
mailing-list messages, etc. A starting point:<br>
git log --stat test/test-multiple.*</p>
<p dir="auto">Apparently, it tests support for what is now considered misnamed<br>
secondary systems, but was once a kind-of-supported feature, seen in<br>
the wild, with nasty consequences sometimes (e.g. infinite loop with<br>
quicklisp until relevant fix).</p>
<p dir="auto">A variable not being rebound is a test that a file hasn't been reloaded.</p>
<p dir="auto">I'd rather not add comments, but I'll review them gladly.</p>
<p dir="auto">—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• <a href="http://fare.tunes.org" style="color:#777" target="_blank">http://fare.tunes.org</a><br>
Everyone hates a martyr. It's no wonder martyrs were burnt at a stake.<br>
— E.W. Howe, "Country Town Sayings", p.7</p>
<p dir="auto">On Mon, Feb 19, 2018 at 5:21 PM, Robert Goldman <a href="mailto:rpgoldman@sift.info" style="color:#777" target="_blank">rpgoldman@sift.info</a> 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">Faré ---</p>
<p dir="auto">Would you please add some comments to test-multiple? I got a failure on<br>
that with MKCL under jenkins on linux, but cannot replicate that failure<br>
running it myself.</p>
<p dir="auto">There's no comment saying what this is supposed to test, other than the<br>
name, which suggests that it's about testing where there are ... multiple<br>
systems defined (incorrectly) in one .asd file? the same systems defined in<br>
multiple .asd files?</p>
<p dir="auto">The test checks to make sure (I believe) that a variable is not rebound when<br>
we ask to reload a system, but not how this pertains to correct ASDF<br>
function.</p>
<p dir="auto">thanks!<br>
r</p>
</blockquote>
</blockquote>
</div></div></div>
</div>
</div>
</blockquote></div><br></div></div></div>