Just committed a workaround allowing European committers to run the build successfully. At least it works for me.
You can easily reproduce the bug by entering a date with year >= 2038. Not sure what is causing the wrong behavior, but it looks like starting from year 2038 any date is broken. BTW: the bug is not present in the hotel booking app. http://tapestry.zones.apache.org:8180/tapestry5-hotel-booking/ On Sun, Aug 14, 2011 at 3:33 AM, Robert Zeigler <[email protected] > wrote: > Since this failure just started being reported, it's likely that it relates > to recent changes, probably the changes I made to fix tap5-1408 and > Tap5-1409. I'll look into it. > > Robert > > GATAATGCTATTTCTTTAATTTTCGAA > > On Aug 13, 2011, at 3:17 PM, Massimo Lusetti <[email protected]> wrote: > > > 2011/8/13 françois facon <[email protected]>: > > > >> since last update from the trunk I get the same error. > >> see the screenshot http://twitpic.com/65j3h4 > >> on the right firefox launch by selenium on left an other firefox > instance > >> > >> with a sudo systemsetup -settimezone Europe/London before the build > >> I get a BUILD SUCCESSFUL > > > > That seems wired and could be a "bug" in firefox or datepicker... I > > will look if it's possible to rewrite the datefield against something > > different then DatePicker... maybe this one: > > http://code.google.com/p/prototype-calendar/ > > > > Cheers > > -- > > Massimo > > http://meridio.blogspot.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Best regards, Igor Drobiazko http://tapestry5.de
