Back from holiday...
The critical part of the test passes with svn, but your testing masked
it. The line number of the failing assert is different in your two
runs - in the first it failed where the bug was, in the second it
failed in your "first sanity check".
That failed because constructing the date-time choose -08:00 rather
than -07:00 now. Adding a offset adjuster (withEarlierOffsetAtOverlap)
allows a simple pick of the required option:
Instant fallFirst1Am = new DateTime().withZone(LOS_ANGELES)
.withDate(2010, 11, 7).withTime(1, 0, 0,
0).withEarlierOffsetAtOverlap().toInstant();
So, the actual problem is fixed in svn
Stephen
On 27 April 2011 16:04, Chris Povirk <[email protected]> wrote:
> Interestingly, it now seems to be broken in the opposite direction:
>
>> expected:<2010-11-07T09:00:00.000Z> but was:<2010-11-07T10:00:00.000Z>
>
> As opposed to the old:
>
>> expected:<2010-11-07T09:00:00.000Z> but was:<2010-11-07T08:00:00.000Z>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today. Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Joda-interest mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/joda-interest
>
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Joda-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/joda-interest
