On 26 November 2017 at 02:18, Glyph wrote:

On Nov 23, 2017, at 6:18 PM, Craig Rodrigues wrote:

Hi,

Can someone update PyPy on the buildbots from PyPy 5.8.0 to PyPy 5.9.0?

I'd love to move PyPy support forward (I even went to the trouble of doing the password-reset dance necessary to get my SSH keys onto these buildbots), but it looks like we have installed from the PPA, which has fallen behind the official releases - https://launchpad.net/~pypy/+archive/ubuntu/ppa/+packages - so upgrading isn't obvious.

Weirdly it looks like Debian is on top of things and does have a current version of the package - https://packages.debian.org/sid/pypy - but I have no clue how to configure these machines to pull just this one package from Debian. If anyone knows how this works, I'd be happy to put more SSH keys on these servers.

My 2 cents. Maybe just run pypy on Travis-CI instead of the buildslaves There is this PR https://github.com/twisted/twisted/pull/226 and ticket https://twistedbumatrix.com/trac/ticket/8505 --------- In that ticket there is one way of solving this. Instead of using using Ubuntu or Debian packages, just use OS independent method to install latest PYPY. Glyph, do we need Debian/Ubuntu packages for PYPY installed on the slaves? ----------- For designing the buildbot builders maybe we can get something similar to Travis-CI. Before running the tests, buildbot will call something like `python admin/buildbot-init` and depending on the environment variables, this script can install various things. In this way we have more configuration logic in the repo and developers can advance the work without waiting for someone to upgrade the OS -- Adi Roiban

On Sat, Nov 25, 2017, at 06:18 PM, Glyph wrote:

...

On Nov 23, 2017, at 6:18 PM, Craig Rodrigues wrote:

Hi,

Can someone update PyPy on the buildbots from PyPy 5.8.0 to PyPy 5.9.0?

I'd love to move PyPy support forward (I even went to the trouble of doing the password-reset dance necessary to get my SSH keys onto these buildbots), but it looks like we have installed from the PPA, which has fallen behind the official releases - https://launchpad.net/~pypy/+archive/ubuntu/ppa/+packages - so upgrading isn't obvious.

Weirdly it looks like Debian is on top of things and *does* have a current version of the package - https://packages.debian.org/sid/pypy - but I have no clue how to configure these machines to pull just this one package from Debian.  If anyone knows how this works, I'd be happy to put more SSH keys on these servers.

Glyph gave me access to the 3 PyPy builders: https://buildbot.twistedmatrix.com/builders/ubuntu16.04-pypy5 I just replaced the system PyPy from the PPA with Squeaky's portable PyPy 5.9.0: https://github.com/squeaky-pl/portable-pypy The PyPy installations are in /opt/pypy_portable/pypy, and their binaries are symlinked into /usr/local/bin. This is documented in ~root/PYPY_README. The builders should now be using PyPy 5.9.0: https://buildbot.twistedmatrix.com/builders/ubuntu16.04-pypy5/builds/172/ste... I have also pinged the maintainer of the Ubuntu PPA about adding PyPy 5.9.0. Once that happens I'll switch the builders back to the PPA. --   Mark Williams   mrw@enotuniq.org

On Wed, Nov 29, 2017, at 05:20 PM, Craig Rodrigues wrote:

Did you install PyPy3 5.9.0 anywhere on the buildbots? It would be good to have that running as well.

Not yet, but I agree! This will require a change to the Buildbot config: https://github.com/twisted-infra/braid/blob/master/services/buildbot/master/... I'll try to do this before the end of the week. --   Mark Williams   mrw@enotuniq.org