./check -v -raw
Failures: 109 132 136 148 152 183

3fd2457d18edf5736f713dfe1ada9c87a9badab1 is the first bad commit
commit 3fd2457d18edf5736f713dfe1ada9c87a9badab1
Author: Peter Xu <[email protected]>
Date:   Fri Mar 9 17:00:03 2018 +0800

    monitor: enable IO thread for (qmp & !mux) typed

    Start to use dedicate IO thread for QMP monitors that are not using
    MUXed chardev.

    Reviewed-by: Fam Zheng <[email protected]>
    Reviewed-by: Stefan Hajnoczi <[email protected]>
    Signed-off-by: Peter Xu <[email protected]>
    Message-Id: <[email protected]>
    Signed-off-by: Eric Blake <[email protected]>


The symptom appears to be extra "RESUME" events in the stream that
weren't expected by the original output for tests 109 and 183; the rest
are python and I didn't dig yet.

./check -v raw
Failures: 055
Failed 5 of 5 tests

91ad45061af0fe44ac5dadb5bedaf4d7a08077c8 is the first bad commit
commit 91ad45061af0fe44ac5dadb5bedaf4d7a08077c8
Author: Peter Xu <[email protected]>
Date:   Fri Mar 9 17:00:05 2018 +0800

    tests: qmp-test: verify command batching

    OOB introduced DROP event for flow control.  This should not affect old
    QMP clients.  Add a command batching check to make sure of it.

    Reviewed-by: Stefan Hajnoczi <[email protected]>
    Signed-off-by: Peter Xu <[email protected]>
    Message-Id: <[email protected]>
    Reviewed-by: Eric Blake <[email protected]>
    Signed-off-by: Eric Blake <[email protected]>



Maybe these are known, but I wanted to consolidate them for rc0 for
something easy to search for. There are others for qcow2 which I'll post
in a bit...!


Thanks,
--js

Reply via email to