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 neologix
Recipients gvanrossum, neologix, r.david.murray, vstinner, yselivanov
Date 2014-07-21.07:08:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1+R3mk5b=Cazi3wvmKqc-wfPSWzab+HAZBc=mUSUimSQ@mail.gmail.com>
In-reply-to <1405498813.74.0.584718927576.issue21901@psf.upfronthosting.co.za>
Content
>> rdmurray@pydev:~/python/p34>python -c 'import resource; print(resource.getrlimit(resource.RLIMIT_NOFILE))'
>> (1024L, 1048576L)
>
> Oh, 1 million files is much bigger than 4 thousand files (4096).
>
> The test should only test FD_SETSIZE + 10 files, the problem is to get FD_SETSITE:

We could cap it to let's say 2**16, it's larger than any possible
FD_SETSIZE (which are usually low since fd_set are often allocated on
the stack and select() doesn't scale well behind that anyway).

But I don't see anything wrong with the test, it's really the buildbot
setting which is to blame: I expect other tests to fail with such a
low max virtual memory.
History
Date User Action Args
2014-07-21 07:08:37neologixsetrecipients: + neologix, gvanrossum, vstinner, r.david.murray, yselivanov
2014-07-21 07:08:37neologixlinkissue21901 messages
2014-07-21 07:08:36neologixcreate