<div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><div dir="ltr">On Mon, Dec 31, 2018 at 12:46 AM Ben Coman <<a href="mailto:btc@openinworld.com">btc@openinworld.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
On Mon, 31 Dec 2018 at 07:20, Fabio Niephaus <<a href="mailto:lists@fniephaus.com" target="_blank">lists@fniephaus.com</a>> wrote:<br>
><br>
> On Mon, 31 Dec 2018 at 12:07 am, Ben Coman <<a href="mailto:btc@openinworld.com" target="_blank">btc@openinworld.com</a>> wrote:<br>
>><br>
>> However SmalltalkCI README indicates it doesn't support 32-bit of latest images for Squeak or Pharo...<br>
>>    <a href="https://github.com/hpi-swa/smalltalkCI#list-of-supported-images" rel="noreferrer" target="_blank">https://github.com/hpi-swa/smalltalkCI#list-of-supported-images</a><br>
>> but is that info current? These files seem to indicate support...<br>
>>    <a href="https://github.com/hpi-swa/smalltalkCI/blob/master/squeak/run.sh" rel="noreferrer" target="_blank">https://github.com/hpi-swa/smalltalkCI/blob/master/squeak/run.sh</a><br>
>>    <a href="https://github.com/hpi-swa/smalltalkCI/blob/master/pharo/run.sh" rel="noreferrer" target="_blank">https://github.com/hpi-swa/smalltalkCI/blob/master/pharo/run.sh</a><br>
><br>
><br>
> Squeak[64]-trunk means Squeak-trunk (32bit) and Squeak64-trunk are supported. Eventually, we want to introduce Squeak32-trunk as well and change the default to 64bit.<br>
> The same rule applies for Pharo.<br>
> Maybe open an issue against smalltalkCI, so we don't forget to get rid of this confusion?<br>
<br>
<a href="https://github.com/hpi-swa/smalltalkCI/issues/407" rel="noreferrer" target="_blank">https://github.com/hpi-swa/smalltalkCI/issues/407</a></blockquote><div><br></div><div>Fixed!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
<br>
>> @vm-dev...<br>
>> I find the specification of the test image too implicit here...<br>
>>    <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/tests/smalltalkCI.sh" rel="noreferrer" target="_blank">https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/tests/smalltalkCI.sh</a><br>
>> For example, its hard to tell at a glance whether lowcode testing is enabled/disabled.<br>
>> Could the test image be explicitly defined in travis.yml ? (I'll submit a concept PR for review)<br>
><br>
><br>
> Please do, happy to review a PR. The current version is still the very first version, I'm sure it can use some improvements :)<br>
<br>
cool.<br>
<br>
btw, are we indeed not testing VMs on Windows?<br>
  <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/.appveyor.yml#L123" rel="noreferrer" target="_blank">https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/.appveyor.yml#L123</a></blockquote><div><br></div><div>I'm afraid you're right. If you could set that up in a similar, that'd be great. smalltalkCI does support AppVeyor:</div><div><a href="https://github.com/hpi-swa/smalltalkCI#appveyoryml-template">https://github.com/hpi-swa/smalltalkCI#appveyoryml-template</a><br></div><div><br></div><div>Fabio</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
cheers -ben<br>
</blockquote></div></div></div>