@pocmatos are the arm runners ok?

Should be… let me check.

oh wait - was too quick to say ‘should be’. I can see what you are referring to. :slightly_smiling_face:

Give me a sec.

oh dear - too many boards… i forgot where racket jobs are running. do you have a screenshot you can send me of the hosted runners we have in the racket org?

pls

oh wait - i think i found them :face_palm:

hummm… interesting - there are jobs running there but there are also many, many github runner processes on the loose which make no sense.

let me restart them, after which I will restart the jobs.

```

```$ uptime 14:47:09 up 188 days, 23:41, 1 user, load average: 1.68, 1.24, 1.23

maybe they really just need a restart.

On that note, I got at the beginning of the week a Mac Mini M1 to setup for Racket testing. :tada:

Never worked on a mac before so even installing basic tools has been a learning experience for me.

Once I get to setup the github runner (which seems to have to use rosetta), I will be asking for a token.

@samth things should now be back online.

Are you using Homebrew?

(… aside from the tools that Xcode provides)

Just installed homebrew… is that how most tools are installed to compile racket?

fwiw, a make cs worked out of the box. :slightly_smiling_face:

Trying to setup the github runner with rosette and then changing the container it runs to arm64, which is githubs recommendation until they have native m1 support.

I don’t think anything in Homebrew is needed to compile Racket; Xcode covers that. I just wanted to recommend Homebrew for anything else Unix-y, in case you didn’t already know.

Well, maybe not Docker. I’ve always installed Docker using the Docker Desktop installer, and I still haven’t tired on M1.

So, maybe it’s not as straightforward as I think. :slightly_smiling_face: