RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1623425 - case 138 of qemu-iotests failed for the result of 'qemu-img check' does not match with the 138.out file
Summary: case 138 of qemu-iotests failed for the result of 'qemu-img check' does not m...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Ademar Reis
QA Contact: Tingting Mao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-29 10:37 UTC by Tingting Mao
Modified: 2019-03-18 21:08 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-18 21:08:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tingting Mao 2018-08-29 10:37:23 UTC 
Description of problem:
Case 138 of qemu-iotests failed, and it seems the reason is that the 138.out file is not matched for the test result.

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.12.0-12.el7
kernel-3.10.0-935.el7

How reproducible:
100%

Steps to Reproduce:
1. Get the source code
# brew download-build --rpm qemu-kvm-rhev-2.12.0-12.el7.src.rpm
# rpm -ivhf qemu-kvm-rhev-2.12.0-12.el7.src.rpm
# rpmbuild -bp /root/rpmbuild/SPECS/qemu-kvm.spec --nodeps 

2. configure the env
# cd /root/rpmbuild/BUILD/qemu-2.12.0/
# ./configure 
# export QEMU_PROG=/usr/libexec/qemu-kvm
# export QEMU_IMG_PROG=/usr/bin/qemu-img
# export QEMU_IO_PROG=/usr/bin/qemu-io
# export QEMU_NBD_PROG=/usr/bin/qemu-nbd

3. test the 82th case
# cd tests/qemu-iotests/
# ./check -qcow2 138



Actual results:
# ./check -qcow2 138
QEMU          -- "/usr/libexec/qemu-kvm" -nodefaults -machine accel=qtest
QEMU_IMG      -- "/usr/bin/qemu-img" 
QEMU_IO       -- "/usr/bin/qemu-io"  --cache writeback -f qcow2
QEMU_NBD      -- "/usr/bin/qemu-nbd" 
IMGFMT        -- qcow2 (compat=1.1)
IMGPROTO      -- file
PLATFORM      -- Linux/x86_64 hp-dl388g8-16 3.10.0-935.el7.x86_64
TEST_DIR      -- /root/rpmbuild/BUILD/qemu-2.12.0/tests/qemu-iotests/scratch
SOCKET_SCM_HELPER -- 

138         - output mismatch (see 138.out.bad)
--- /root/rpmbuild/BUILD/qemu-2.12.0/tests/qemu-iotests/138.out	2018-04-24 12:30:47.000000000 -0400
+++ /root/rpmbuild/BUILD/qemu-2.12.0/tests/qemu-iotests/138.out.bad	2018-08-29 06:32:58.943135380 -0400
@@ -5,5 +5,6 @@
 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=512
 wrote 512/512 bytes at offset 0
 512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+tcmalloc: large alloc 140737488363520 bytes == (nil) @  0x7f5d98ac935f 0x7f5d98ae9bd6 0x7f5d985ea826 0x55d269fd28f1 0x55d269fd4e63 0x55d269fd57e1 0x55d269fd5aac 0x55d269fd6096 0x55d269fcdad1 0x55d269fcdb44 0x55d269fa84c3 0x55d26a07c16a 0x7f5d96808010
 qemu-img: Check failed: Cannot allocate memory
 *** done
Failures: 138
Failed 1 of 1 tests


Expected results:
The case could pass.

Additional info:
Comment 2 Ping Li 2018-09-03 15:00:00 UTC 

*** This bug has been marked as a duplicate of bug 1331279 ***
Comment 3 CongLi 2018-09-04 03:26:13 UTC 
(In reply to Tingting Mao from comment #0)
> Description of problem:
> Case 138 of qemu-iotests failed, and it seems the reason is that the 138.out
> file is not matched for the test result.

QE would like to report each failed iotests case separately with detailed reason, which is more clear and more quick to fix it, instead of a list of failed iotests cases.

Thanks.
Comment 5 Ademar Reis 2019-03-18 21:08:36 UTC 
Our downstream CI team is now running qemu-iotests. Several of them are even enabled in %check as part of rpmbuild.

The ones that are broken in the CI or brew environment are being reported in bugzilla (there are several reported already).

So I'm closing all of the old qemu-iotest BZs. We'll work on them in this more controlled environment of CI and brew.
Note You need to log in before you can comment on or make changes to this bug.