PyPy 3 builds on travis are timing out

[pfmoore]

Logging this here because I don't know where else to log it, or what we can do about it. Master is currently failing on travis because the PyPy 3 build is timing out. I've restarted it a couple of times, but it's the same each time. The PyPy builds have always been slow, but is travis particularly overloaded at the moment?

I don't know how important it is that we run the tests on PyPy 3.

[pradyunsg]

@pfmoore I'd opened #4846 about this before.

[pradyunsg]

I don't know how important it is that we run the tests on PyPy 3.

Same here. It's probably something interesting, likely some behaviour that we're hitting of PyPy 3 here or it's just really bad at I/O heavy tasks. 🤷‍♂️

[pfmoore]

Ta. I'll close this as it's a dupe of #4846.

I have basically no personal interest in PyPy 3, and I'd be very surprised to find we had a lot of pip users on PyPy 3, but I can't justify removing it from the test config just on my preferences. But conversely, I've never seen anything that explains why we added it, or what our level of support for it is intended to be.

I'll go back to ignoring it, I guess. Mostly I just felt guilty because the last commit to master was mine, so travis started sending the "build has failed" emails to me :-)

[pradyunsg]

Cool. :)

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.