Comment 3 for bug 575037

The LOSAs gave me a failed build to look at. The surface-level problem can actually be seen in the traceback:

File "/home/pqm/for_rollouts/production/eggs/zope.security-3.7.1-py2.5-linux-x86_64.egg/zope/security/management.py", line 22, in <module>
ImportError: cannot import name interfaces

Notice that egg directory: zope.security-3.7.1-py2.5-linux-x86_64.egg . The x86_64 suffix indicates that this egg was built for a 64 bit machine. However, it is being run on a 32 bit machine.

I did not determine the underlying piece of software that does not detect the problem and force a rebuild. Discovering that does not seem valuable at this time, since we want to change the way we generate these eggs anyway, soon.

Instead, the LOSAs and I agreed that I would create a different target for the build machine. Instead of running ``make bin/buildout && bin/buildout`` on that machine, I will make an "build_eggs" target, so they will run ``make build_eggs`` instead. It's implementation should look something like this: http://paste.ubuntu.com/439560/

Doing this adds about 5.671 seconds to the buildout run per machine, if my instance is any indication.