shuppy

I think the runner labelling approach would definitely solve the problem where two jobs get assigned to self-hosted runners when only one is available. That said, would we still be...

> This should happen very rarely (for server to be shutdown at the right moment), we can still use timeout job for that case, but this time the job failure...

I got close in [this build](https://github.com/delan/servo/actions/runs/10487795220/job/29048921433) ([commit](https://github.com/delan/servo/commit/11547c3b5c0404f4d72d96cdc845cb477bb486c6))! But the magic GITHUB_TOKEN [doesn’t have permission](https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication) to read or write runner labels, even if we [set `permissions` to `write-all`](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/controlling-permissions-for-github_token). The docs say...

All done! I’m using a personal access token scoped to the org for now, which will require manual renewal once a year, but I’ll look into GitHub App installation access...

> I am not able to test this with pushing to try on servo/servo: https://github.com/servo/servo/actions/runs/10507371415/job/29108982963. Are runners and secrets set? Sorry, I was in the middle of rebaking the Windows...

@sagudev, runners should be up now!

> Oh I did not see that one. I hope @delan won't mind and that we can push something to the finish line :) No worries! I haven’t had time...

Do not open the link in the comment above. VirusTotal for exe in rar:

We are preparing an intent to prototype this in Chromium (cc @schenney-chromium, @jihyerish). Based on this issue and the discussion in #5233 and #5522, it seems there are a few...

Breaking out the two easier questions for the agenda: #10212 + #10213