<div dir="ltr">Hi Frank,<div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 17, 2014 at 12:44 AM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 16 November 2014 03:24, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
> Hi All,<br>
><br>
> problems solved. So new VMs available at<br>
> <a href="http://www.mirandabanda.org/files/Cog/VM/VM.r3137/" target="_blank">http://www.mirandabanda.org/files/Cog/VM/VM.r3137/</a>.<br>
<br>
</span>OK, so in CI this manifests (in<br>
<a href="http://build.squeak.org/job/SqueakTrunkOnSpur/101/console" target="_blank">http://build.squeak.org/job/SqueakTrunkOnSpur/101/console</a>) as<br>
"Segmentation fault".<br></blockquote><div><br></div><div>I htink I'm in the clear. I see this from lines immediately preceeding the launch:</div><div><br></div><pre style="white-space:pre-wrap;word-wrap:break-word;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-size:11px">curl -sSo cogspurlinux.tgz <a href="http://www.mirandabanda.org/files/Cog/VM/VM.r3133/cogspurlinuxht-14.45.3133.tgz" style="color:rgb(92,53,102)">http://www.mirandabanda.org/files/Cog/VM/VM.r3133/cogspurlinuxht-14.45.3133.tgz</a>
</pre><div><br></div><div>So I don't think you're testing 3137. Fingers crossed.</div><div><br></div><div>perhaps putting a <span style="color:rgb(0,0,0);font-size:11px;white-space:pre-wrap">cogspurlinux/squeak </span>-version in the script to print the version before doing the proper launch would be a good idea.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Currently the build conflates several tests: it tests the latest<br>
released CogSpur while trying to update the image. That means that<br>
"segmentation fault" could actually arise because of a broken VM, or<br>
from something during the update. I _think_ that we can distinguish<br>
between the two cases, because during update we should see more<br>
output, like a stack trace or similar. For instance<br>
<a href="http://build.squeak.org/job/SqueakTrunkOnSpur/100/console" target="_blank">http://build.squeak.org/job/SqueakTrunkOnSpur/100/console</a> shows that<br>
the VM (3126) did indeed load the image, and something went wrong<br>
during an update.<br>
<span class=""><font color="#888888"><br>
frank<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">best,<div>Eliot</div></div>
</div></div>