Skip to content
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

Add case for specific max sector of disk #3152

Merged

Conversation

qingwangrh
Copy link
Contributor

ID:2035698
Signed-off-by: qingwangrh [email protected]

@qingwangrh
Copy link
Contributor Author

python ConfigTest.py --testcase=block_iscsi_with_specical_max_sectors --guestname=RHEL.9.0.0 --driveformat=virtio_scsi,virtio_blk --machines=q35,i440fx --clone=no
(1/4) Host_RHEL.m9.u0.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.0.0.x86_64.io-github-autotest-qemu.block_iscsi_with_specical_max_sectors: PASS (667.16 s)
(2/4) Host_RHEL.m9.u0.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.0.0.x86_64.io-github-autotest-qemu.block_iscsi_with_specical_max_sectors.q35: -PASS (671.31 s)
(3/4) Host_RHEL.m9.u0.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.0.0.x86_64.io-github-autotest-qemu.block_iscsi_with_specical_max_sectors: PASS (672.29 s)
(4/4) Host_RHEL.m9.u0.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.0.0.x86_64.io-github-autotest-qemu.block_iscsi_with_specical_max_sectors.q35: PASS (661.22 s)

@qingwangrh qingwangrh force-pushed the 2035698_add_case_specific_max_sector branch 2 times, most recently from 531bba6 to 1e5b5e5 Compare December 27, 2021 06:22
@qingwangrh
Copy link
Contributor Author

@zhencliu @zhenyzha Please help to review it. Thanks.

@qingwangrh qingwangrh force-pushed the 2035698_add_case_specific_max_sector branch from 1e5b5e5 to ab9198f Compare December 27, 2021 10:26
@zhenyzha
Copy link
Contributor

git am 3152.patch
Applying: Add case for specific max_sector_kb of disk

 (1/4) Host_RHEL.m9.u0.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.8.6.0.aarch64.io-github-autotest-qemu.block_iscsi_with_specical_max_sectors.arm64-pci: PASS (708.23 s)
 (2/4) Host_RHEL.m9.u0.qcow2.virtio_blk.up.virtio_net.Guest.RHEL.9.0.0.aarch64.io-github-autotest-qemu.block_iscsi_with_specical_max_sectors.arm64-pci: PASS (705.54 s)
 (3/4) Host_RHEL.m9.u0.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.8.6.0.aarch64.io-github-autotest-qemu.block_iscsi_with_specical_max_sectors.arm64-pci: PASS (716.94 s)
 (4/4) Host_RHEL.m9.u0.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.0.0.aarch64.io-github-autotest-qemu.block_iscsi_with_specical_max_sectors.arm64-pci: PASS (715.54 s)

Current cmd is recorded in debug.log, and the cmd output is in session.log. But this's also the phenomenon in other cases, so ok for me.

@zhencliu
Copy link
Contributor

LGTM

@zhencliu zhencliu merged commit e10dc80 into autotest:master Dec 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants