On Fri, Mar 23, 2018 at 01:36:28PM -0500, Eric Blake wrote: > On 03/23/2018 01:30 PM, Christian Borntraeger wrote: > > > > Even that didn't work - 'make check' fails with either 1/4 or 4/4 applied > > > in isolation, so I'm squashing them into a single patch. > > > > Yes, "qmp: introduce QMPCapability" added an assert, that was fixed by a > > later on patch. So > > the original series was not bisectable. Anyway with Peters 4 patches all > > applied things are fine > > for me. > > Weird, since I seem to recall running 'make check' on every patch in order > in that series without seeing failures, prior to preparing the pull request > (where I fell short was running iotests, which is what sparked this whole > revert thread). Anyways, even if my memory is faulty and the original > series has a broken bisection window, it's now water under the bridge; the > focus at this point is improving the known bugs to see if we can re-enable > OOB prior to -rc2.
I think each of the commit in original series should pass "make check" before. But for this revert series, it can't. I'll take this into consideration next time even reverting patches. Regarding to the revert ordering itself: IMHO as long as we do the first patch last (put "Revert monitor: enable IO thread for (qmp & !mux) typed" at the end), we should be able to pass "make check" too. So the correct order should be: patch 2-4 (in any order, since each of them is only a test case) patch 1 And, since at it, I just noticed that we could even keep one of the test ("tests: qmp-test: verify command batching"), but anyway it won't hurt if we revert that too now. -- Peter Xu