On 03/23/2018 10:53 AM, Eric Blake wrote:
Actually, we should revert things in reverse order of the original
commits, so that we aren't introducing yet more temporary breakage.
Since you reverted:
$ git describe 3fd2457 d003f7a 91ad450 0213031 --match=v\*
v2.11.0-2595-g3fd2457d18e
v2.11.0-2598-gd003f7a8f9c
v2.11.0-2597-g91ad45061af
v2.11.0-2585-g02130314d8c
where the higher the middle number represents the further distance from
2.11 (aka newer patch), this series should be applied in the order:
2/4 (revert the newest patch first)
3/4
1/4
4/4
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.
The failure was either:
GTESTER check-qtest-x86_64
**
ERROR:tests/qmp-test.c:96:test_qmp_protocol: assertion failed: (entry)
GTester: last random seed: R02Sa02aeb0d46d3092524914cd9be2b57f7
make: *** [/home/eblake/qemu/tests/Makefile.include:880:
check-qtest-x86_64] Error 1
or:
GTESTER check-qtest-x86_64
**
ERROR:tests/qmp-test.c:92:test_qmp_protocol: assertion failed:
(capabilities && qlist_empty(capabilities))
GTester: last random seed: R02S621a9dbfcf7bed132c614953e93ecb37
make: *** [/home/eblake/qemu/tests/Makefile.include:880:
check-qtest-x86_64] Error 1
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
