My laptop is running 64-bit Linux (14.10).  It has 4.6GB of free disk space.  Naturally that's not enough to run test_mmap.

When I run the test suite, test_mmap consumes all available disk space, then fails.  (Hopefully freeing all its temporary files!)  If I used "-j" to run more than one test at a time, this usually means *other* tests fail too, because I'm running multiple tests in parallel and there are plenty of other tests that require, y'know... any disk space whatsoever.

The documentation for the test suite ("./python -m test -h") says that "-u largefile" allows tests that use more than 2GB.  Surely test_mmap's delicious 800PB tests should be marked largefile-enabled-only?

I'd like to see this fix backported to 3.4 too.  And if 2.7 shows this behavior, maybe there too.