[squeak-dev] Failing tests on CI

Frank Shearar frank.shearar at gmail.com
Thu Mar 14 10:00:19 UTC 2013


On 13 March 2013 22:41, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>
>
> On Tue, Mar 12, 2013 at 2:13 PM, Nicolas Cellier
> <nicolas.cellier.aka.nice at gmail.com> wrote:
>>
>> It seems that this one would pass after a Compiler recompileAll, maybe
>> we should add some postInstall action somewhere after environments
>> changes...
>
>
> Yes, but a simple recompile will result in lots of unbound methods.  We need
> to do something more principled that I thought ReleaseBuilder did.  Frank,
> you were working on this right?

Yes, but this is _before_ the ReleaseBuilderFor4dot5 kicks in. The
tests are failing in the SqueakTrunk job, and it's only
ReleaseSqueakTrunk that does all this (specifically, `Compile
recompileAll`). And of course it's a one-way trip;
ReleaseSqueakTrunk's artifact isn't fed back into SqueakTrunk. (And it
shouldn't, because ReleaseSqueakTrunk is supposed to take an
ever-shrinking trunk core and add expected goodies to produce a
standard image.)

Er, unless I miss the point: are you asking if we do any better than
`Compiler recompileAll`?

frank

>> http://build.squeak.org/job/SqueakTrunk/223/testReport/Tests.Compiler/MethodHighlightingTests/testMethodHighlighting/
>>
>> Nicolas
>>
>
>
>
> --
> best,
> Eliot
>
>
>


More information about the Squeak-dev mailing list