Taking a look at github ci failures for beman.scope, none of them seem to be real issues – just CI communication failures/timeouts, etc. In my survey this is only llvm test runs that are having the problem.
Now it’s possible scope is behind the curve on the latest CI setup so maybe I need to update it. Do we have a process in place for that now?