Around the time I was realizing a stable bisect wasn't going to be likely, I started receiving alerts from AWS about the testing instance. Shut it down, started a new one. Not seeing issues any more.
On Mon, Jun 30, 2014 at 12:43 PM, Andrew Purtell <[email protected]> wrote: > I did another bisect and landed somewhere else. The results are not > stable. Trying again with more reps per run. If that doesn't work, we will > have to treat the symptom. > > > On Sun, Jun 29, 2014 at 11:35 AM, Andrew Purtell <[email protected]> > wrote: > >> A bisect with more test suite repetitions per step lead to 34ae4a9 >> (HBASE-11094: Distributed log replay is incompatible for rolling restarts). >> Bisecting again to see if the results are stable. >> >> >> On Thu, Jun 26, 2014 at 1:39 PM, Andrew Purtell <[email protected]> >> wrote: >> >>> I'm finding that repeated runs of the unit test suite at the head of >>> branch 0.98 intermittently fail. Individual tests do not, so this likely a >>> lagging shutdown, port/resource conflict, and/or zombie test issue. I am >>> currently bisecting commits on 0.98 branch since the last release in the >>> hope of pinning this down to a single change. Depending on how quickly that >>> can happen, the RC might happen on Monday or not. As things stand at the >>> head of the branch, I'd not +1 the RC given the release criteria I've been >>> using up to now. >>> >>> >>> On Tue, Jun 24, 2014 at 6:09 PM, Andrew Purtell <[email protected]> >>> wrote: >>> >>>> Planning to roll the 0.98.4 RC on Monday 6/30. >>>> >>>> I should have done it this week. Sorry, got a little sidetracked. >>>> >>> > > -- > 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)
