
@jesse has joined the channel

@samth can you please check the arm64 runner is there and green pls? https://docs.github.com/en/actions/hosting-your-own-runners/adding-self-hosted-runners#checking-that-your-self-hosted-runner-was-successfully-added-1

@jesse welcome! :slightly_smiling_face:


no errors on your side…

Jul 10 17:29:58 rpi4 runsvc.sh[20724]: Starting Runner listener with startup type: service
Jul 10 17:29:58 rpi4 runsvc.sh[20724]: Started listener process
Jul 10 17:29:58 rpi4 runsvc.sh[20724]: Started running service
Jul 10 17:30:05 rpi4 runsvc.sh[20724]: √ Connected to GitHub
Jul 10 17:30:06 rpi4 runsvc.sh[20724]: 2020-07-10 15:30:06Z: Listening for Jobs

no errors on my side…


:disappointed:

grrr

I assume you’ve done all the troubleshooting things

I believe “This check failed” without additional error message indicates internal error

I tested everything - will restart the board and service and try again.

Strange because it worked with my pmatos/actions-test
repo.

But then the runner was repo-wide instead of org-wide.

I wonder if there are some lurking bugs in this new org-wide runner. organization wide runners are a new feature so it wouldn’t surprise me.

i will try to downgrade to the previous runner version and see.

@samth could you check repo permissions for the runner: https://docs.github.com/en/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners

does it say the runner can be used for all repos in the org?

i will wait for the check before downgrading. I have no ideas left.

Ahah. Can you try now

oh YES!!!

on my end: Jul 10 17:37:47 rpi4 runsvc.sh[1266]: 2020-07-10 15:37:47Z: Listening for Jobs
Jul 10 18:54:47 rpi4 runsvc.sh[1266]: 2020-07-10 16:54:47Z: Running job: build-arm64
Jul 10 18:54:54 rpi4 runsvc.sh[1266]: 2020-07-10 16:54:54Z: Job build-arm64 completed with result: Succeeded


now we can proceed with actually configuring the job.

Thanks @samth!!!

It was set to only be allowed on private repositories.

argh… next hurdle. bogdan’s setup racket does not work for non-intel archs: https://github.com/racket/ChezScheme/runs/858849681#step:3:10

maybe just start from the C code instead of using setup-racket

Right - you mean building sgc, right?

Just noticed we also need to build the racket/racket-ci
image for arm32 and arm64 to get this working.

Yes

after we get racket ci for arm32 and arm64 we should use the latest built snapshot of racket instead, but we’ll get there later.