[squeak-dev] And another thing; updating broken by recent time fetching upheaval

David T. Lewis lewis at mail.msen.com
Sun Feb 21 01:12:59 UTC 2016

On Sat, Feb 20, 2016 at 04:25:58PM -0800, tim Rowledge wrote:
> > On 20-02-2016, at 7:57 AM, David T. Lewis <lewis at mail.msen.com> wrote:
> > 
> > The failure seems to intermittent for me. I tried updating the same
> > image several times. It failed a couple of times but usually the updates
> > completed without error.
> How odd. I???m not at all sure how intermittent could occur with what we hoped was a deterministic update, but there we are, reality strikes again.

I don't know. I've been away all day, and checking it again now I can't
get it to fail any more. Is anyone still having trouble updating their
trunk image?

Intermittent issues would not be entirely surprising in a case like this.
Anything involving Monticello is going to do a lot of DateAndTime stuff,
and there are various processes in your image that are also doing
Chronology things. If things get out of whack for a short period of
time during updating, it is certainly possible that intermittent errors
might happen.

These discussions are part of the reason that I think it will be a good
thing when we get Chronology moved into its own package. It is also the
reason that I am nervous about doing the package move, because it
introduces the possibility of totally screwing up the update stream.


More information about the Squeak-dev mailing list