On Wed, Feb 08, 2012 at 09:45:36AM -0600, Chris Muller wrote:
> I could fix the TimeStamp tests but, as I mentioned, since TimeStamp
> is planned for purging from the image, my preference would be to just
> do that now...  Addition-by-subtraction..   :)

That sounds reasonable.

Dave

> 
> On Wed, Feb 8, 2012 at 7:41 AM, David T. Lewis <lewis at mail.msen.com> wrote:
> > On Wed, Feb 08, 2012 at 08:04:59AM -0500, David T. Lewis wrote:
> >> On Tue, Feb 07, 2012 at 09:41:12PM -0600, Chris Muller wrote:
> >> > > Here is the system report from a fresh image running on Linux with an
> >> > > interpreter VM. I started with a fresh 4.3 image, did an update from
> >> > > trunk, then loaded Kernel-cmm.670 from the inbox and ran the tests.
> >> >
> >> > You need KernelTests-cmm.214 too.
> >>
> >> D'oh! My apologies.
> >>
> >> With the test updates loaded, The chronology tests are green with
> >> time zone set to UTC, and show nine failures in TimeStampTest and
> >> one failure in TimeStampDoTest.
> >
> > Sorry, that was horribly unclear. What I meant to say is that the
> > failures show up when I use my local time zone setting, which is
> > currently 5 hours from UTC for me. This is the "LT" time zone that
> > is used by default in a fresh image. The failures go away when I
> > set the time zone to UTC (which is not the setting that I would
> > normally use).
> >
> > Dave
> >
> >>
> >> What time zone are you using (DateAndTime localTimeZone)? If your
> >> time zone offset has a zero duration, please try setting it to something
> >> else, and check the effect on the tests.
> >>
> >> Dave