update buildbot version

[mattip]

This is the first issue in this new repo. It is a port of the mercurial buildbot, as it states in the README. We should

• add the testing to github actions and run the tests on new commits
• update the buildbot infrastructure from 0.8 + python2.7 to something more modern

@StanFromIreland you expressed some interest in this idea?

The current buildbot has been running for quite some time, and has massive history. The mirror directory of PyPy downloads (./public/html/mirror) is 37GB, the ./bench_results of old benchmark runs is 72MB, the master/* record of old runs is 13GB. We don't want to lose that.

[mattip]

It seems there is a basic problem. Buildbot 0.8 was the last to support the status API that makes the summary page happen. So if we are to move forward, we need to rethink that. One option would be

• move all the runners to github actions. They support the 6 platforms (for now, macos x86_64 is going away soon but I guess we don't care): linux64, linux32, linux_arm64, macos-x86_64, macos-arm64, windows with native runners.
• write a small website that does the summary pages. It would download the pytest results from github and then parse them very much like the current code does. The server running the site would continue to host the binaries.

[mattip]

I did the second bullet in https://github.com/pypy/build-summary. It is a small flask app that copies the ux of pypy's buildbot, without managing the builds. It has *_sync scripts to download buldbot runs, nightlies, and benchmark results.

[StanFromIreland]

Hi sorry I missed your ping, yes, I'm interested.

[mattip]

My fault you didn’t see the ping, i set this up private and just today made it public.