I feel like this might have something to do with us enabling Sista while
using relatively old VMs for trunk images on CI.

Can anyone verify that the VMs running on Travis come with the Sista
bytecode set?

Fabio

On Tue, 10 Mar 2020 at 8:48 pm, Jakob Reschke <forums.jakob at resfarm.de>
wrote:

> Am Di., 10. März 2020 um 20:42 Uhr schrieb Eliot Miranda
> <eliot.miranda at gmail.com>:
> >
> > On Tue, Mar 10, 2020 at 12:13 PM tim Rowledge <tim at rowledge.org> wrote:
> >>
> >> > On 2020-03-10, at 12:08 PM, Jakob Reschke <forums.jakob at resfarm.de>
> wrote:
> >> >
> >> > Hello,
> >> >
> >> > Christoph's idea of having alerts whenever the Trunk builds in
> >> > smalltalkCI get broken sounds like a good one. @Fabio is it possible
> >> > to set up a dummy repository that does not really load anything, but
> >> > runs the Squeak base test suite? Or load an empty dummy package and
> >> > run the test suite of a different package?
> >> >
> >> > This time something goes wrong while setting a VM parameter.
> >> > Unfortunately it does not tell you where it really happens:
> >> >
> >> > Preparing Squeak64-trunk image for CI...
> >> > ................................................Error:
> vmParameterAt:put: failed
> >>
> >> That sounds interestingly similar to the problem I reported with the
> linuxARMv6 vm in the 5.3 release package...
> >
> >
> > Any stack traces?  Which parameter, which value was being assigned, etc?
> >
> > "Something went wrong" is rather vague...
>
> I know, unfortunately Travis does not provide any more specific output. :-(
> Maybe I can try to run smalltalkCI on my machine later and see whether
> that gives anything.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200310/91f2c0e7/attachment.html>