Ah - ok, john didn’t merge CI changes onto the release branch so the CI files in the release branch were broken.
@samth what’s the core team policy here? Once we are preparing for release, should we merge CI changes straight into the release branch or ask John (Clements) to do it?
Why do I feel that 7.7 has significantly more crash reports compared to other releases…
I think if you want changes merged to the release we should discuss it
No backports now. I was thinking for future releases.
Right, I understand. What I mean is that in the future, if there’s some CI change that should go on the release branch, we should talk about it.
Either it really has more problems or users are more involved.
I think there are two bugs reported so far, one of which was a packaging regression, and one of which was an old bug
@pocmatos can you add a few things to your testdeps docker image (so that I can run the installers more easily with act)?
In particular, sudo, node, wget, and the other packages installed in ci-snapshots.yml (https://github.com/nodesource/distributions/blob/master/README.md#installation-instructions)
Yes! I can improve that. Not today as I am sorting out racket news but I will take a look at that tomorrow.
where’s the source code for that? I can send a PR
Isn’t it in racket/racket?
@samth there they are.
:slightly_smiling_face:
I am getting slightly fed up with the Actions hosted runner. There seems that there’s no single commit lately that doesn’t fail because of the runner. :disappointed:
yeah, they seem to be having serious reliability issues
@pocmatos does the PR with the Dockerfile change look good?
if so, you adding that to the actual docker images would be convient for me
Trying to get my kids to bed but I will take a look soon.
thanks
@samth why node?
bogdan’s action needs it
ah! :slightly_smiling_face:
those docker images will now be built automatically by docker
both racket/racket-ci:builddeps and racket/racket-ci:testdeps
ah - perfect, so you sorted it. Great - thanks! :slightly_smiling_face: