This isn't going to happen today either. I am tracking down why some tests for the hbase-server module leave multiple surefire runners hanging around. Really weird stuff, ClockOutOfSyncExceptions yet I checked and my system clock is only drifting a handful of milliseconds from NTP pool time at any given moment.
On Thu, Jan 23, 2014 at 9:38 AM, Andrew Purtell <[email protected]> wrote: > JIRA is back. Tonight around midnight PST (crosses fingers, going to be > hard to get work done today in that state) > > > On Wed, Jan 22, 2014 at 9:50 PM, Andrew Purtell <[email protected]>wrote: > >> Yep JIRA's indexes are still broken, searches for 'fix version' etc are >> returning 500s. Until tomorrow. >> >> >> On Wednesday, January 22, 2014, Andrew Purtell <[email protected]> >> wrote: >> >>> JIRA has been unavailable or throwing 503s for a few hours now. This >>> will have to wait one day. >>> >>> >>> On Wed, Jan 22, 2014 at 3:58 PM, Andrew Purtell <[email protected]>wrote: >>> >>> That test failure was not reproducible on my build boxes. >>> >>> Last call for commits that already have a +1 for 0.98 branch, I am >>> tagging RC0 around midnight tonight Pacific time. >>> >>> After that please consider the "soft freeze" over and done, my earlier >>> request complete. I still reserve the right to revert inappropriate commits >>> to 0.98 branch as RM, so it would be good to check first on changes that >>> are new features or may be controversial. >>> >>> >> >> -- >> Best regards, >> >> - Andy >> >> Problems worthy of attack prove their worth by hitting back. - Piet Hein >> (via Tom White) >> >> > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
