This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients alexis, eric.araujo, flox, francismb, higery, jlove, nadeem.vawda, paul.moore, pitrou, python-dev, rpetrov, tarek, vinay.sajip, westley.martinez
Date 2011-11-05.21:47:28
SpamBayes Score 3.051759e-11
Marked as misclassified No
Message-id <1320529639.81705.YahooMailNeo@web25803.mail.ukl.yahoo.com>
In-reply-to <1320502072.62.0.624058674116.issue13193@psf.upfronthosting.co.za>
Content
> FTR, I haven't checked this on Ubuntu 32-bit. It's rather odd for the

> failure to be architecture-dependent. Are these two machines running
> different versions of Ubuntu, perhaps?

They are (Ubuntu Natty 32-bit failing, Ubuntu Oneiric 64-bit passing).
However, I don't believe the failure is directly architecture-related, but
indirectly so. For example, test execution order might not be identical
on all machines, depending for example on hash values and dict bucket
sizes, which I would expect to be different on different machines for any
number of reasons. In my limited testing, I found the following:

Ubuntu Natty 32-bit - failed.
Windows 7 32-bit - failed.
Ubuntu Oneiric 64-bit - passed.
Linux Mint "Katya" 11 64-bit (based on Ubuntu Natty) - passed.

With non-deterministic test execution order combined with module-level
data updated by tests, it can be hard to reproduce these failures - a bit
like uninitialised data errors in C :-(
History
Date User Action Args
2011-11-05 21:47:29vinay.sajipsetrecipients: + vinay.sajip, paul.moore, pitrou, nadeem.vawda, tarek, eric.araujo, rpetrov, flox, alexis, westley.martinez, python-dev, jlove, higery, francismb
2011-11-05 21:47:28vinay.sajiplinkissue13193 messages
2011-11-05 21:47:28vinay.sajipcreate