
So the plan to fix the release branch is:
- Update the release branch of chezscheme to https://github.com/racket/ChezScheme/commit/83221c32b4e8654f0f7d3b3857b7efab5be2bad4 (the last commit of 9.5.3.32).
- Use https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags to split “Checking out ChezScheme” to two. One for release branch and another for the rest.
Is this correct?
It looks like the main Makefile
also contains a reference to “https://github.com/racket/ChezScheme”. Is it run by any workflow at all?

I think @pocmatos would know if that’s used, but I think the fact that make
on the release
branch doesn’t work should hopefully be fixed too

we are checking out chezscheme manually, not from the makefile.

Today I have quite a bit of work and then I still have to finalize and publish RN so I am in a bit of pinch.

otoh, i just merged arm64 testing to chez.

I can try to look into the release branch issue tomorrow morning.

but like @sorawee it should be a matter of doing the same thing but cloning the release branch of chez instead of doing - name: Checking out ChezScheme
working-directory: ./racket/src
run: git clone --depth=1 --recurse-submodules -j3 <https://github.com/racket/ChezScheme>

this is in line 168 of ci-push_linux.yml
.

oh wait - there’s better way.

ok, one sec.

Another thing is, this would fix the error appeared under GitHub Actions, but who’s the one that will actually build the official Racket 7.8? And is the script to build it fixed, too?


John Clements builds the release, and I’m confident that process works

That uses a lot of infrastructure that is not used in most of the CI

The release branch of ChezScheme is currently pointing to a commit from last year. Are you suggesting that John has a branch that tracks ChezScheme commits for release elsewhere?

For repositories that don’t have a current release branch, usually the commit on branch day is recorded.

Ah, I see.


I’m not certain exactly how the process works for racket/ChezScheme
since it isn’t tracked via a catalog.

untested but should work

from PR to merge in 30 secs. thanks - that must be some sort of record. :slightly_smiling_face:

Oh, I think there’s “Checking out ChezScheme” in ci-push_macos
and scanbuild_static-analysis
too

Need to change those as well?

can someone else do it for the other platforms? I am starting a meeting now. Sorry!

Yep, will do

otherwise i will check it later on

@sorawee thank you!