On 30.03.2017 04:16, Eric Blake wrote: > On 03/29/2017 09:01 PM, Ed Swierk via Qemu-devel wrote: >> Parts of qemu's block code have changed a lot in recent months but are >> not well exercised by current tests. >> >> Subtle bugs have crept in causing assertion failures, hangs and other >> crashes in a variety of situations: immediately on start, on first >> guest activity, on external snapshot create or commit, on qmp quit >> command. >> >> Reproducing these bugs has proved tricky, as each may occur only with >> a specific combination of qemu version, block device type (virtio-blk >> or virtio-scsi) and iothread enabled or not. In some cases the bug >> occurs only after several external snapshot operations. And in some >> cases the bug only manifests when a guest is accessing the block >> device simultaneously. >> >> I've written an iotest (number 176, for now) that attempts to cover > > At least one other thread has already proposed a test 176. It's > somewhat straightforward to renumber things, but I'm wondering if there > is some even-more-efficient way of reserving test numbers, perhaps > through the wiki, since we are finding that test numbers get reserved > several weeks before actually getting merged into the tree.
As a maintainer, I don't mind collisions; I can and will rename tests. For all I care, you can even name all of your tests 001. Max
signature.asc
Description: OpenPGP digital signature
