[Vm-dev] CI status

David T. Lewis lewis at mail.msen.com
Mon Oct 26 14:54:01 UTC 2020


On Mon, Oct 26, 2020 at 03:22:39PM +0100, Nicolas Cellier wrote:
>  
> Le lun. 26 oct. 2020 ?? 15:11, Eliot Miranda <eliot.miranda at gmail.com> a
> ??crit :
> 
> >
> > Hi Nicolas,
> >
> > On Oct 26, 2020, at 6:59 AM, Nicolas Cellier <
> > nicolas.cellier.aka.nice at gmail.com> wrote:
> >
> > ???
> > Hi all,
> > I have restored (I think) the green status of minheadless build.
> >
> >
> > Thank you so much!
> >
> > We could eventually authorize failure of all those builds, or restrict the
> > number of flavours that we build (it takes really loooong time before we
> > get CI feedback).
> > But if we abandon all those now, I fear that we never catch up; it's a one
> > way ticket. IMO there are still interesting ideas to take, even if
> > development has continued in Pharo fork...
> >
> >
> > One approach might be to split them into ???essential??? and ???nice to have??? so
> > we get faster feedback from the ???essential??? set.
> >
> > +1, but I do not know how to configure the CI like that...
> 
> > Now the next failing build on travis is about squeak.cog.v3. Did some
> > incompatible VM change took place?
> >
> > For example
> > https://travis-ci.org/github/OpenSmalltalk/opensmalltalk-vm/jobs/738831149
> >
> > ######################################################
> >
> > # Squeak-4.6 on Travis CI (2278.23)                  #
> >
> > # 3401 Tests with 5 Failures and 0 Errors in 112.13s #
> >
> > ######################################################
> >
> > #########################
> >
> > # 5 tests did not pass: #
> >
> > #########################
> >
> > SUnitToolBuilderTests
> > 837fef_266b
> >
> >  ??? #testHandlingNotification (10023ms)
> >
> > TestValueWithinFix
> > 2a65cb_266b
> >
> >  ??? #testValueWithinTimingBasic (1005ms)
> > e9a7ab_266b
> >
> >  ??? #testValueWithinTimingNestedInner (1001ms)
> > c57415_266b
> >
> >  ??? #testValueWithinTimingNestedOuter (1002ms)
> > e89da3_266b
> >
> >  ??? #testValueWithinTimingRepeat (3004ms)
> >
> >   Executed 3401 Tests with 5 Failures and 0 Errors in 112.13s.
> >
> > To reproduce the failed build locally, download smalltalkCI, and try to run something like:
> >
> > 	bin/smalltalkci -s Squeak-4.6 --headfull /path/to/.smalltalk.ston
> >
> > Could these test failures be nothing to do with the VM but instead to do
> > with the (growing) divergence between trunk/spur and Squeak 4.6?
> >
> > _,,,^..^,,,_ (phone)
> >
> No idea...
> I've downloaded a Squeak4.6-15102.image, compiled a squeak.cog.v3 on
> windows10, and the test pass...
> I will retry on other OSes this evening (the test fails on linux...).

I do not know if it is related to the CI issues, but here is one clue:

I am maintaining a V3 "trunk" image that attempts to keep in sync with
trunk except for changes that pertain to Spur object format (immediate
characters, etc). As of Monticello-ul.728 I get failures in SSL connection
to e.g. source.squeak.org. The failures happen with both Cog and the
interpreter VM (although the specific error symptoms are different).

I can bypass the errors by reverting MCHttpRepository>>httpGet:arguments:
to its prior version (stamped ul 9/20/2019).

I have not had time to dig into the underlying cause of the problem,
but it seems likely that any CI test for Cog that requires the use
of secure sockets will fail as of Monticello-ul.728 or later. This
would include any test that needs to access the source.squeak.org
repository.

Dave



More information about the Vm-dev mailing list