Bug 180659
Summary: | mysql fails to build in rawhide | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jesse Keating <jkeating> |
Component: | mysql | Assignee: | Tom Lane <tgl> |
Status: | CLOSED WORKSFORME | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | byte, dcantrell, hhorak |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-10 01:51:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jesse Keating
2006-02-09 19:30:51 UTC
Worked fine when I built it. I noticed that in the failed run, spud was building both the s390 and s390x ports, and it was running the mysql regression tests in both buildroots at the time of the failure. I suspect that there is some interaction when multiple copies of the regression tests run concurrently in a single machine. Our RPMs already take several measures to prevent such interaction, such as forcing different TCP port numbers to be used, but perhaps there is still something there. Or maybe mysql is just flaky ;-). But I've seen test failures before with multiarch machines building both arches concurrently, and never when it's running by itself. Disinclined to spend more time on it right now. |