@pocmatos interesting error here: https://github.com/racket/racket/runs/335319196#step:9:60

Humm. That’s an horrendous failure on macos. I am confused as to why it happened. Haven’t seen the commit yet but feels strange that it would break this. Tempted to press rerun all checks again but concerned things will pass the second time around and I will never understand what happened. Will take a look in the morning.

I don’t have a mac, sadly. One thing you could try is downloading the artifacts from that and seeing if you can reproduce.

I don’t have a mac either. :disappointed:

I have been considering a mac mini just for racket development but even the minis are quite expensive.

Seems to be flaky - since it passes now - but I don’t get how. I will play around with this git sha on my fork to force a ci rebuild.

I pushed a branch to my fork at the point of failure but Actions was too smart and decided not to test because it noticed it had already CI’ed this git sha, so I forced it by removing a readme. :wink: I am not sure if I want this to pass or to fail: https://github.com/LinkiTools/racket/commit/ef008ef8c29797e6e600f69a73d142ea8c23c03f/checks?check_suite_id=345153596

@samth do you use windows? I am stuck with splitting the windows 3m and cs builds and would need a hand from someone who knows the command line windows build process. I have been taking shots in the dark but it’s not working.