
@pocmatos am I correct in understanding that runner.temp not being found in a container-based github action is a bug?


yes, a github bug.

ok

what’s happening is that inside the container temp is actually /__w/temp

ok

and currently ${{ runner.temp}}
and a bunch of other variables are broken.

Either dump containers for now or hardcode the proper paths.

ok

Can’t believe they haven’t noticed this until now…

I mean… are we really the first ones to hit this in 6 months (at least) of GitHub Actions

?!?!?

I will probably just use the Racket s3-sync package

anyway, an engineer contacted me and he said h would let me know once a fix is deployed.

do you have a link to the discussion?

btw, that action is me working on doing installer snapshots in GHA

Awesome! Thanks. That sounds great. Will take a look at the code because I wanted to generate snapshots for non intel archs as well.

Does this mean installers in https://www.cs.utah.edu/plt/snapshots/ will get built right away? (as opposed to having to wait 24 hours)

that’s the idea


This errors AWS_ACCESS_KEY_ID is not set. Quitting.

Have you fixed it before merging? Otherwise, all builds from now on will fail I think

Oh, I failed to set those, thanks for reminding me. But it can’t work on the PR because those don’t see secrets.

can we also get docker images for installer snapshots?

that would probably require more work (and me learning more about docker)

I was thinking of adding them to the jackfirth/racket
docker image repository somehow

so you could do docker run jackfirth/racket:7.6.009
(or however the version numbers for snapshots work)

since the version number does not change on every commit, I’m just addressing them by hash


Yes, and you can now download http://snapshot.racket-lang.org/ci-snapshots/a4b5fe5b7812aff682f18edf41525b16fcda743e/racket-x86_64-linux.sh and it should work