On Mon, Sep 12, 2016 at 4:56 PM, Peter Maydell <peter.mayd...@linaro.org> wrote: > On 12 September 2016 at 16:12, Peter Maydell <peter.mayd...@linaro.org> wrote: >> On 12 September 2016 at 15:08, Stefan Hajnoczi <stefa...@redhat.com> wrote: >>> The following changes since commit c2a57aae9a1c3dd7de77daf5478df10379aeeebf: >>> >>> Merge remote-tracking branch 'remotes/famz/tags/docker-pull-request' into >>> staging (2016-09-09 12:49:41 +0100) >>> >>> are available in the git repository at: >>> >>> git://github.com/stefanha/qemu.git tags/block-pull-request >>> >>> for you to fetch changes up to 8f1096787517c66b67cc29bab65edc0188a86326: >>> >>> tests: fix qvirtqueue_kick (2016-09-12 15:06:29 +0100) >> >> >> /replication/primary/get_error: OK >> /replication/secondary/get_error: OK >> >> Please can you rename these tests? They create false positives in >> scripts that look in the build logs for errors by grepping for >> "error:" or "warning:". > > Also, two new sanitizer errors: > > /home/petmay01/linaro/qemu-for-merges/block/qcow2.c:1807:41: runtime > error: null pointer passed as argument 2, which is declared to never > be null > /home/petmay01/linaro/qemu-for-merges/block/qcow2-cluster.c:86:26: > runtime error: null pointer passed as argument 2, which is declared to > never be null > > both attempts to memcpy() from a NULL source pointer while running > the tests/test-replication test.
These sanitizer errors cannot be introduced by this pull request because no patches touched block/qcow2.c or block/qcow2-cluster.c. Strange. I will add a patch to fix them anyway. Stefan
