-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
block_during_io: modify 'iozone' value to ensure the stress alive #4260
base: master
Are you sure you want to change the base?
Conversation
The case purpose is to test shutdown or reboot guest during IO, Sometimes iozone stress test already completed before run the shutdown or reboot, so the case will error. Signed-off-by: menli <[email protected]>
(2/2) Host_RHEL.m10.u0.ovmf.qcow2.virtio_blk.up.virtio_net.Guest.Win11.x86_64.io-github-autotest-qemu.block_during_io.iozone_stress.system_disk.send_qmp.with_system_reset.q35: PASS (297.84 s) |
@peixiu please help to review it when you free, thanks |
python ConfigTest.py --testcase=block_during_io.iozone_stress --guestname=Win10 --platform=x86_64 --driveformat=virtio_scsi --clone=no --customsparams="cdrom_virtio = isos/windows/virtio-win-prewhql-0.1-271.iso" (1/6) Host_RHEL.m*.u0.ovmf.qcow2.virtio_scsi.up.virtio_net.Guest.Win10.x86_64.io-github-autotest-qemu.block_during_io.iozone_stress.system_disk.send_qmp.with_system_reset.q35: STARTED Tested with the latest code, all job passed. Thank you! |
@XueqiangWei please help review it when you free, thanks |
The case purpose is to test shutdown or reboot guest during IO, Sometimes iozone stress test already completed before run the shutdown or reboot, so the case will error.
ID: 3372