Aaruni Kaushik

Sorry, I missed your notification from two weeks ago. Yes this has been superseded by the already merged PR #3650

Thanks for the update for the rest of the class (people like me, not on discord). Really appreciate the work you guys are putting in. Working on some other projects,...

The Linux runners are on the `oscarci-tester` account and setup with systemd user units, so they should come online automatically after server restarts. I am still reading up on macOS...

> which was 3 days ago I made the change last evening, and re ran just the short test, to make sure nothing is broken as a side effect. But...

Note, that we have just done a separation of the depots, there is still no "cleanup" phase which removes stuff for a fresh start.

Github runners do allow Pre / Post hook scripts ( https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/running-scripts-before-or-after-a-job ), so, a decision needs to be made about what we should do in the cleanup phase, and then...

This PR *replaces* the github hosted runners by the RPTU runners. This means all tests are expected to be very fast, but if the RPTU runners ever go offline, testing...

Reverted unnecessary cosmetic changes, and let the CI run this time. However, the "required" tests will no longer run (as they are required on `ubuntu-latest`, which we don't test anymore)....

The unit file for the runner now controls `NUMPROCS`, and also adds system limits at 600% CPU (corresponding to NUMPROCS=6), and 8 GB of RAM (MemoryMax is set to 8G,...

Looks like 8 GB is far too low a limit. Runners need some amount of memory per core: trying to watch htop during testing, a little more than 4 GB...