Was thinking about the script to build/test racket, which I would prefer to write in Racket but…
If the idea is to use them to build racket cross-arch, this means we need a racket cross-arch.
hummm, actually if we use a debian cross-arch container, debian ships racket at least for arm so we could use that.
Otherwise for other archs, we could create an unofficial distribution just to CI racket ports.
ok, thanks.
What if we put the prefix somewhere known, like $HOME/install, and create that directory?
Then it doesn’t matter what GitHub does
That would work but the problem is that I don’t know what kind of permissions we have. We can try… :slightly_smiling_face:
we can run as root if needed
also we should definitely have permissions under $HOME
I am not even sure which user we run as… maybe I have seen it before but cannot remember.
Will create a dummy project and test.
@samth no point in talking in thread when it’s just us. :slightly_smiling_face:
You are right!
We are user runner , home is /home/runner
and we have permissions at home.
Lets install everything to $HOME/install?
yes, that sounds good to me
can you do that? I’m not sure I’d get all the places.
I can do then - not sure I can reuse your PR. Might have to create a new one.
If that’s ok with you, I will do it now.
Yes, I can just close mine.
OK - I was looking at the docs because we cannot use $HOME in working-directory: tags.
It turns out that github has ${{ runner.temp }} to use which might be a good idea to use. Docs here: https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#runner-context
What do you think?
that also seems fine
but why do we need to set working-directory?
For upload/download artifact actions. You don’t have access to the shell to change directory.
will be impressed if I got all the paths right. Need to leave now for a bit, will come back later.
Lets see what CI says in the meantime.
There are still several uses of .. in the file — in the windows build and in the scanbuild steps. Should those change too?
right - there’s a missing one, now fixed. All good with .. in scan-build report mgm and windows build
Do we need to change the ci-pr file?
Don’t think so… there was a problem… with working directory on a uses. Will fix.
Wow - I am stumped by the current failures in scanbuild jobs for 3m and cs: https://github.com/racket/racket/runs/609803669?check_suite_focus=true#step:8:207
They can’t find racketcgc binary but configure just said in the previous step the binary path is correct.
it seems to be building 3m in the previous step, and then not finding cgc?
right…
although I just noticed that when configure says: hey, we are using racket FOO, it doesn’t actually check FOO exists.
It’s getting late here. I would like to fix the current scanbuild issue but unsure if I will make it.