Issue with PyPy on Travis

All jobs are now failing on pypy, see this job. Locally I cannot replicate this with pypy2.7-X, but the same thing does fail with “Too many open files” in pypy3.6-7.1.0. It’s very hard to debug this. @gaborbernat replicated it on a macbook, he similarly can’t replicate the 2.7 failure, and the 3.6 failure is a different error message than the one I have.

There may be two problems here, possibly with similar causes. I think it’s possible that Travis has scaled down the amount of memory available and that’s biting us in the pypy2.7 job? Hard to tell.

If we want a short-term mitigation, we can maybe try:

1. Try updating the pypy version in the job.
2. Try migrating the pypy job in Azure Pipelines (though that would require getting #1721 working.

This is a major blocking issue IMO.

[gaborbernat]

pypy3 --version                                                                                                                                                          9.5s  Wed  3 Apr 10:51:14 2019
Python 3.6.1 (dab365a465140aa79a5f3ba4db784c4af4d5c195, Feb 18 2019, 10:53:27)
[PyPy 7.0.0-alpha0 with GCC 4.2.1 Compatible Apple LLVM 10.0.0 (clang-1000.11.45.5)]

[webknjaz]

@pganssle FTR now you can use just pypy and pypy3 values in Travis CI config and it will get you Python 2.7.13 (8cdda8b8cdb8, Apr 14 2019, 14:06:44) [PyPy 7.1.1 with GCC 6.2.0 20160901] and Python 3.6.1 (784b254d6699, Apr 14 2019, 10:22:42) [PyPy 7.1.1-beta0 with GCC 6.2.0 20160901] there.