<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
> <span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Can anyone verify that the VMs running on Travis come with the Sista bytecode set? </span><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Both Squeak 5.2 and Squeak 5.3 release VMs support the SistaV1 bytecode set.</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Best,</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Marcel</span></div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 10.03.2020 23:13:06 schrieb Fabio Niephaus <lists@fniephaus.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">
<div><div><div dir="auto">I feel like this might have something to do with us enabling Sista while using relatively old VMs for trunk images on CI.</div><div dir="auto"><br></div><div dir="auto">Can anyone verify that the VMs running on Travis come with the Sista bytecode set? </div><div dir="auto"><br></div><div dir="auto">Fabio</div></div></div><div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 10 Mar 2020 at 8:48 pm, Jakob Reschke <<a href="mailto:forums.jakob@resfarm.de" target="_blank">forums.jakob@resfarm.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda<br>
<<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>>:<br>
><br>
> On Tue, Mar 10, 2020 at 12:13 PM tim Rowledge <<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>> wrote:<br>
>><br>
>> > On 2020-03-10, at 12:08 PM, Jakob Reschke <<a href="mailto:forums.jakob@resfarm.de" target="_blank">forums.jakob@resfarm.de</a>> wrote:<br>
>> ><br>
>> > Hello,<br>
>> ><br>
>> > Christoph's idea of having alerts whenever the Trunk builds in<br>
>> > smalltalkCI get broken sounds like a good one. @Fabio is it possible<br>
>> > to set up a dummy repository that does not really load anything, but<br>
>> > runs the Squeak base test suite? Or load an empty dummy package and<br>
>> > run the test suite of a different package?<br>
>> ><br>
>> > This time something goes wrong while setting a VM parameter.<br>
>> > Unfortunately it does not tell you where it really happens:<br>
>> ><br>
>> > Preparing Squeak64-trunk image for CI...<br>
>> > ................................................Error: vmParameterAt:put: failed<br>
>><br>
>> That sounds interestingly similar to the problem I reported with the linuxARMv6 vm in the 5.3 release package...<br>
><br>
><br>
> Any stack traces? Which parameter, which value was being assigned, etc?<br>
><br>
> "Something went wrong" is rather vague...<br>
<br>
I know, unfortunately Travis does not provide any more specific output. :-(<br>
Maybe I can try to run smalltalkCI on my machine later and see whether<br>
that gives anything.<br>
<br>
</blockquote></div></div>
</div>
</div></blockquote>
</div></body>