[squeak-dev] Is the FileList broken in trunk?

Frank Shearar frank.shearar at gmail.com
Sat Dec 14 23:13:49 UTC 2013


On 14 December 2013 20:53, Chris Muller <asqueaker at gmail.com> wrote:
> Hi Frank!  I actually put this message out to lure you into this discussion.
> :)  Because, I want to move on 4.5 and I knew you had _something_ out there,
> but couldn't remember all the details.

You used the right kind of bait, that's for sure :)

> The issues I faced with needing to get a new image were:
>
 > - I had to research the mailing list to find out where to download it.  An
> automated build server is great for doing continuous *testing* and
> reporting, but it seems like for end-user downloads we should have a copy
> available at the usual place (ftp.squeak.org).
> - When I downloaded the image from CI, updated, and ran the tests, I found
> there were more tests failing than in another image that was simply updated
> from 4.4.  Something seemed to be wrong with the image state.
> - Since I was not really certain what all was done in that image, I could
> not trust putting it on the squeak.org FTP site.  The only way I could be
> SURE enough about the state of an image put there was to take the archive
> release image (4.4) and simply update it myself and save it.
>
> So, the overarching requirements:
>
>   - Downloadable from squeak.org domains.
>   - A way to know exactly how it was built:  This means knowing which prior
> _full release image_ was started with, and what changes (both code and
> objects) were made.
>   - Reproducible build.  My idea since 4.2 was to have a utility method on
> ReleaseBuilder do all of this so it would be visible straight in the trunk
> repository.  I guess I always thought of the CI's responsibility as a
> on-going "test-status reporting" mechanism more than a deployment tool.

Yep, yep, yep. I agree with all the above.

There is something wrong with the base image state at the moment,
partly because I'm incapable of pulling out ToolBuilder-Tests in less
than at least three attempts (sigh!). (*)

So the idea I've always had with CI was this:
* take a known-good base image (not happening right now :( )
* update it
* run a battery of tests on a copy of the image
* run the release process on the image (ReleaseSqueakTrunk)

Every now and then, someone can take the latest ReleaseSqueakTrunk
artifact, takes a look at the test results on build.squeak.org, plays
around with it. If it's fit for purpose, he or she pushes the artifact
up to ftp.squeak.org as a release candidate. Everyone else bangs on
it, and if the release manager's happy, it ships.

I do think that manual verification is important, because we don't
want random broken builds on ftp.squeak.org, even if they're declared
as alpha quality.

Additionally, as you rightly point out we need someone to advertise
build.squeak.org. Not just that it's there and we use it, but how to
get a bleeding-edge image, for instance.

frank

(*) This causes problems like this guy -
http://build.squeak.org/job/SqueakTrunk/678/testReport/junit/Morphic.ToolBuilder/MorphicToolBuilderTests/testWindowDynamicLabel/
- because that TestCase's superclass is obsolete.

>  - Chris
>
>
> On Sat, Dec 14, 2013 at 2:24 PM, Frank Shearar <frank.shearar at gmail.com>
> wrote:
>>
>> That's great for easing David's pain - something well worth doing
>> (especially since I'm almost certainly a large contributing factor) -
>> but as a general rule, if we can't use the automated builds to do
>> this, I need to know, so I can fix it. Because we should, in a later
>> version than 4.4, be producing and publishing artifacts in a
>> completely automated fashion. We're not _quite_ there yet, but I need
>> to know any shortcomings in the process if we're ever to reach that
>> happy day.
>>
>> frank
>>
>> On 14 December 2013 20:21, Chris Muller <asqueaker at gmail.com> wrote:
>> > The alpha image is nothing more than an updated 4.4 image (clicking
>> > through
>> > all the merge requests), trimming MC cache, save image, done.
>> >
>> >
>> > On Sat, Dec 14, 2013 at 2:20 PM, Chris Muller <asqueaker at gmail.com>
>> > wrote:
>> >>
>> >> Dave just FYI I recently posted a new alpha image at
>> >> http://ftp.squeak.org/4.5-alpha.  Filelist works there and it is
>> >> currently
>> >> basis for moving toward a release.
>> >>
>> >>
>> >> On Sat, Dec 14, 2013 at 8:23 AM, David T. Lewis <lewis at mail.msen.com>
>> >> wrote:
>> >>>
>> >>> On Fri, Dec 13, 2013 at 05:05:27PM -0800, tim Rowledge wrote:
>> >>> >
>> >>> > On 13-12-2013, at 4:50 PM, David T. Lewis <lewis at mail.msen.com>
>> >>> > wrote:
>> >>> >
>> >>> > > I cannot open a file list (world -> open... -> file list) in a
>> >>> > > fully
>> >>> > > updated trunk image.
>> >>> > >
>> >>> > > Is it just me?
>> >>> >
>> >>> > Possibly; my latest was -297 which worked ok and I just updated to
>> >>> > 321
>> >>> > and opening the filelist works ok. OS X 10.9, iMac, Cog vm. Only
>> >>> > thing I
>> >>> > noticed was a merge dialog popping up relating to some ST80 packages
>> >>> > stuff.
>> >>> >
>> >>>
>> >>> It is indeed my image. I took another much older image and updated it
>> >>> fully
>> >>> to trunk, and the file list works fine.
>> >>>
>> >>> Sorry for the noise.
>> >>>
>> >>> Dave
>> >>>
>> >>>
>> >>
>> >
>> >
>> >
>> >
>>
>
>
>
>


More information about the Squeak-dev mailing list