test.yml: run on self-hosted [6.1.x]#214
Conversation
|
@fredvd It keeps failing with the same error when using the latest I wonder if the self-hosted needs some updates. I half remember you mentioning that maybe the self-hosted runner would no longer be needed. Am I remembering correctly? |
|
Did you see my other PR where I update to the setup qemu v4 recipe. Because that's were the 6.1.5 release was hanging AFAICS #215 |
|
@fredvd For 6.1.5, https://github.com/plone/plone-backend/actions/runs/28202583156/job/83626409945 There may be some randomness involved. |
Currently, `test.yml` works, see [this run](https://github.com/plone/plone-backend/actions/runs/28202581450) from PR #421, which upgrades to Plone 6.1.5. But then the release of 6.1.5 (via `image-release.yml`) fails, see [this run](https://github.com/plone/plone-backend/actions/runs/28202583156/job/83626409863). Big difference: the release runs on `self-hosted`. Let's first see if `test.yml` also starts failing when run on `self-hosted`. Then we can see if we can fix that. It goes wrong in `docker/setup-buildx-action@v3`: ``` Error response from daemon: failed to stat parent: stat /var/lib/containerd-stargz-grpc/snapshotter/snapshots/15190/fs: no such file or directory ``` There are lots of differences between self-hosted and the standard ubuntu, some older, some newer. An obvious thing to try it just to move to latest `docker/setup-buildx-action@v4`. But that is for later.
As expected, `test.yml` [fails](https://github.com/plone/plone-backend/actions/runs/28404941277/job/84165176967?pr=214#step:6:198) now that is is run on `self-hosted`. So we try the first fix: use the latest version of the setup-buildx-action.
e94e6a5 to
52d06e9
Compare
|
@fredvd I have rebased on 6.1.x to get your version changes, and I have updated the versions in the other files, but the test run still fails, now with: |
|
|
Currently,
test.ymlworks, see this run from PR #421, which upgrades to Plone 6.1.5.But then the release of 6.1.5 (via
image-release.yml) fails, see this run.Big difference: the release runs on
self-hosted.Let's first see if
test.ymlalso starts failing when run onself-hosted.Then we can see if we can fix that. It goes wrong in
docker/setup-buildx-action@v3:There are lots of differences between self-hosted and the standard ubuntu, some older, some newer. An obvious thing to try it just to move to latest
docker/setup-buildx-action@v4. But that is for later.BTW, 6.2.1 has the same problem. But let's try on one branch for now.