Bug 1237120 - Koji build hosts: "buildhw-" vs "buildvm-"
Summary: Koji build hosts: "buildhw-" vs "buildvm-"
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: koji
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mike McLean
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-30 12:28 UTC by Marek Skalický
Modified: 2016-12-20 13:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 13:52:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marek Skalický 2015-06-30 12:28:40 UTC
Description of problem:
For some time I have a problem with building of MongoDB in koji. It is because some tests are failing...
However this is very strange. I am not able to reproduce it to my rawhide virtual machine (also upstream is not possible to reproduce it). For more that two weeks I have been trying different build combinations,... to figure out where and why this fail is occurring.

The testsuite is failing with:
going to run test: ThreadedTests::Slack<mongo::SimpleRWLock, mongo::SimpleRWLock::Exclusive>N5mongo12SimpleRWLockE Slack useful work fraction: 0.764695 locks:117504
dbtest: /usr/include/boost/thread/pthread/condition_variable_fwd.hpp:86: boost::condition_variable::~condition_variable(): Assertion `!ret' failed.
2015-06-30T10:59:10.594+0000 F -        [testsuite] Got signal: 6 (Aborted).

Mainly this occurs for x86_64. And sometimes it pass fine.

I thought that this could depend on "host" in koji. After last successful build I noticed that host's name started with "buildhw-". I've checked it and all successful builds were hosted on "buildhw-" hosts and failed build on "buildvm-" hosts...

What is the difference among these host configurations?

Version-Release number of selected component (if applicable):
Version used in actual Fedora infrastructure - koji.fedoraproject.org

How reproducible:

For example this two scratch-builds are from the same srpm

https://koji.fedoraproject.org/koji/taskinfo?taskID=10236799
https://koji.fedoraproject.org/koji/taskinfo?taskID=10250790

Actual results:
First build succeeded, second build failed.

Expected results:
Both builds succeeded.

Additional info:

Comment 1 Jan Kurik 2015-07-15 13:53:22 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

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

Comment 2 Fedora Admin XMLRPC Client 2016-03-10 14:45:38 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Dennis Gilmore 2016-03-10 17:24:11 UTC
buildhw- builders are physical, and buildvm- are virtual machines. the physical machines have more ram and cpu

Comment 4 Fedora End Of Life 2016-11-24 11:58:18 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2016-12-20 13:52:16 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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