Bug 1100971 - test failing on s390
Summary: test failing on s390
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 22
Hardware: s390
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2014-05-24 16:28 UTC by Dan Horák
Modified: 2016-03-17 01:09 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-17 01:09:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dan Horák 2014-05-24 16:28:01 UTC
starting with qemu-2.0.0-0.1.rc0.fc21 some tests fail on s390

from build.log
...
  LINK  tests/qom-test
  CC    tests/tmp105-test.o
  CC    tests/libqos/i2c-omap.o
  LINK  tests/tmp105-test
  CC    tests/spapr-phb-test.o
  LINK  tests/spapr-phb-test
GTESTER check-qtest-i386
blkdebug: Suspended request 'A'
blkdebug: Resuming request 'A'
(process:37423): GLib-ERROR (recursed) **: (NULL) messageBroken pipe
GTester: last random seed: R02Sc99c8ee27f7e085f239dbf56744d4499
[vmxnet3][WR][vmxnet3_peer_has_vnet_hdr]: Peer has no virtio extension. Task offloads will be emulated.
make: *** [check-qtest-i386] Error 1

for a full log please see http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1411763

As this happens only on s390 (32-bit), I'm disabling the tests there. This not a priority issue I think.


Version-Release number of selected component (if applicable):
qemu-2.0.0-4.fc21

Comment 1 Jaroslav Reznik 2015-03-03 15:50:29 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 2 Cole Robinson 2016-03-17 01:09:14 UTC
Just closing this... not sure if it's still an issue but tests have been a recurring issue on s390. I'll keep this bug referenced in the spec file


Note You need to log in before you can comment on or make changes to this bug.