-
Notifications
You must be signed in to change notification settings - Fork 172
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
virtio_mode: updates PCI patterns according to the numerical ID #3777
Conversation
(01/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_netkvm.with_modern.q35: STARTED
(01/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_netkvm.with_modern.q35: PASS (52.62 s)
(02/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_netkvm.with_transitional.q35: STARTED
(02/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_netkvm.with_transitional.q35: PASS (53.91 s)
(03/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_netkvm.with_legacy.q35: STARTED
(03/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_netkvm.with_legacy.q35: PASS (53.43 s)
(04/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_builtin.with_modern.q35: STARTED
(04/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_builtin.with_modern.q35: PASS (54.49 s)
(05/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_builtin.with_transitional.q35: STARTED
(05/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_builtin.with_transitional.q35: PASS (53.90 s)
(06/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_builtin.with_legacy.q35: STARTED
(06/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_builtin.with_legacy.q35: PASS (54.55 s)
(07/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_random.with_modern.q35: STARTED
(07/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_random.with_modern.q35: PASS (54.77 s)
(08/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_random.with_transitional.q35: STARTED
(08/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_random.with_transitional.q35: PASS (54.24 s)
(09/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_random.with_legacy.q35: STARTED
(09/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_viorng.with_rng_random.with_legacy.q35: PASS (55.26 s)
(10/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_vioscsi.with_modern.q35: STARTED
(10/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_vioscsi.with_modern.q35: PASS (54.38 s)
(11/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_vioscsi.with_transitional.q35: STARTED
(11/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_vioscsi.with_transitional.q35: PASS (54.43 s)
(12/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_vioscsi.with_legacy.q35: STARTED
(12/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_vioscsi.with_legacy.q35: PASS (54.72 s)
(13/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_balloon.with_modern.q35: STARTED
(13/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_balloon.with_modern.q35: PASS (55.69 s)
(14/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_balloon.with_transitional.q35: STARTED
(14/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_balloon.with_transitional.q35: PASS (55.63 s)
(15/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_balloon.with_legacy.q35: STARTED
(15/15) Host_RHEL.m9.u3.qcow2.virtio_scsi.up.virtio_net.Guest.RHEL.9.3.0.x86_64.io-github-autotest-qemu.virtio_mode.with_balloon.with_legacy.q35: PASS (54.24 s)
RESULTS : PASS 15 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0 |
@yanglei-rh @qingwangrh @PaulYuuu @yanan-fu @XueqiangWei Please could you review this PR? Thanks! |
This solution could be applied to #3768 (or the #3768 solution to this PR). IMHO, and following the developer's advice, we need to focus only in the numerical ID, as the name ID (previous pattern) can change without notice. Keeping in mind the current supported PCI IDs, it's possible to look for 0.9 or 1.0 virtio devices IDs in the same execution, avoiding possible failures in the future if any of the names change. What do you think? @yanglei-rh @qingwangrh @PaulYuuu @yanan-fu @XueqiangWei |
Test Pass: |
LGTM |
Agree with using the numerical ID, it is more standard and uniform. |
13725a8
to
73da6cf
Compare
@yanan-fu included now, thanks! |
73da6cf
to
35141d0
Compare
35141d0
to
ac21441
Compare
Updates the case logic, checking the numerical ID of the PCI devices instead of the full name, that could be updated without notice. In order to support 0.9 and 1.0 virtio devices, the pattern now contains both IDs. Signed-off-by: mcasquer <[email protected]>
ac21441
to
defc74f
Compare
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack
Could this PR be merged? Thanks! |
virtio_mode: updates PCI patterns according to the numerical ID
Updates the case logic, checking the numerical ID of the PCI devices
instead of the full name, that could be updated without notice.
In order to support 0.9 and 1.0 virtio devices, the pattern now
contains both IDs.
Signed-off-by: mcasquer [email protected]
ID: 2222179