Tests work today. Any known commons issue for this? I could probably reproduce this by setting my system clock to 13 March 2016 or 14 March 2016 after 03:00 sometime.
On 14 March 2016 at 09:50, Matt Sicker <[email protected]> wrote: > Failed tests: > FixedDateFormatTest.testFormatLong:147 > ABSOLUTE(HH:mm:ss,SSS)/1457876956930 expected:<0[8]:49:16,930> but > was:<0[7]:49:16,930> > FixedDateFormatTest.testFormatLongCharArrayInt:181 > ABSOLUTE(HH:mm:ss,SSS)/1457876956767 expected:<0[8]:49:16,767> but > was:<0[7]:49:16,767> > FixedDateFormatTest.testFormatLongCharArrayInt_goingBackInTime:199 > ABSOLUTE(HH:mm:ss,SSS)/1457931593422 expected:<2[3]:59:53,422> but > was:<2[2]:59:53,422> > FixedDateFormatTest.testFormatLong_goingBackInTime:163 > ABSOLUTE(HH:mm:ss,SSS)/1457931593331 expected:<2[3]:59:53,331> but > was:<2[2]:59:53,331> > > The stack traces from the tests are all comparison failures, so they're > just assertion errors. > > -- > Matt Sicker <[email protected]> > -- Matt Sicker <[email protected]>
