Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 834538 - libosinfo-0.1.2-1 is FTBFS on ARMv5tel
Summary: libosinfo-0.1.2-1 is FTBFS on ARMv5tel
Alias: None
Product: Fedora
Classification: Fedora
Component: libosinfo
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
Reported: 2012-06-22 09:36 UTC by Peter Robinson
Modified: 2012-07-16 10:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-07-16 10:55:29 UTC
Type: Bug

Attachments (Terms of Use)

Description Peter Robinson 2012-06-22 09:36:26 UTC
One of the tests fails

test-loader.c:36:E:Core:test_basic:0: (after this point) Test timeout expired
FAIL: test-loader

Comment 1 Daniel Berrangé 2012-06-25 12:25:22 UTC
Our test suite has timeouts enabled

[quote 'info check']
To be certain that a test won't hang indefinitely, all tests are run
with a timeout, the default being 4 seconds.  If the test is not
finished within that time, it is killed and logged as an error.

   The timeout for a specific test case, which may contain multiple unit
tests, can be changed with the `tcase_set_timeout()' function.  The
default timeout used for all test cases can be changed with the
environment variable `CK_DEFAULT_TIMEOUT', but this will not override
an explicitly set timeout.  Another way to change the timeout length is
to use the `CK_TIMEOUT_MULTIPLIER' environment variable, which
multiplies all timeouts, including those set with
`tcase_set_timeout()', with the supplied integer value. All timeout
arguments are in seconds and a timeout of 0 seconds turns off the
timeout functionality.

Given that we know ARM is a pretty slow architecture, I expect we need to just increase the default timeout, to longer than 4 seconds, since some of our tests are quite long even on x86.

You can test whether this fixes arm by editing the RPM spec and changing %check to use


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