'make build' failed during the rollout when importing zope.security.management
Bug #575037 reported by
Björn Tillenius
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Gary Poster |
Bug Description
During the last rollout (2010-05-04), some machines failed on the 'make build' step, when zope.security.
Here's the log files from building on the importds:
https:/
This error also happened on forster. Doing a 'make clean; make build' made it work, but we need to find out why this happened, and prevent it from happening again.
Related branches
lp:~gary/launchpad/bug575037
- Māris Fogels (community): Approve
-
Diff: 61 lines (+17/-8)1 file modifiedMakefile (+17/-8)
Changed in launchpad-foundations: | |
status: | Triaged → Fix Released |
status: | Fix Released → Fix Committed |
tags: | added: qa-ok |
tags: | added: canonical-losa-lp |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad-foundations: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I tried duping by building more and more like the deployment does it, with consultation by mthaddon, but everything worked fine for me locally (last attempt: https:/ /pastebin. canonical. com/32158/ ).
Then we hit on this (edited):
[12:20pm] mthaddon: gary: those two servers are x86, fwiw
[12:20pm] mthaddon: gary: as opposed to most which are amd64
[12:20pm] gary: mthaddon: ah-hah. So, all the 32 bit machines were unhappy, all the 64 bit were happy?
[12:21pm] mthaddon: gary: it does seem that way, yeah (forster is 32 bit as well)
[12:21pm] mars: gary, mthaddon, and the eggs you are building and moving around architecture independent?
[12:22pm] gary: mars, no, dependent, but eggs have identifiers for the architecture. The 32 bit machines build their own eggs
[12:22pm] gary: or are supposed to, and have done so in the past
Since 32 bit/64 bit seems implicated, I'll try seeing if I can dupe this locally with virtual machines.