Simon Josefsson simon@josefsson.org writes:
I must admit I forgot what you were using my amd64 runner for,
I use if for a dozen build jobs, both native builds in various configurations, and cross builds with qemu tests. And then the special s390x job that uses ssh to my IBM test vm.
just got approved for a permenant s390x virtual machine from IBM (the community VM's I had seems to expire after a couple of weeks...) and I will setup a proper GitLab runner on it. Assuming I'm successful with this, I'm happy for nettle to use it too.
That would be nice!
Thus I would recommend to just remove the 'tag: amd64' from your .gitlab-ci.yml, enable 'Run untagged jobs' for my amd64 runner if you want to keep it, and things should work everywhere?
If I rememer correctly, the reason I originally added tags to these jobs were that at gitlab.com the jobs were sometimes picked up by runners on macos or windows, and then they failed miserably.
I've now tried adding the "Run untagged jobs" for the runner. So if I understand it correctly, the tags don't belong to the runner machinery itself, they are attached on the association between runner machines and gitlab projects?
I've also pushed a branch ci-delete-tags-amd64 where I delete the tags from .gitlab-ci.yml.
But then I think managed to somehow botch something on the gitlab instance related to the nettle project or my account (possible pressing reload at the wrong time when changing the ci/cd settings), and at the moment I get 403 on everything when logged in (if I open a new private browser tab, I get working public view, which goes back to 403 on everything once I login). So I'm a bit stuck there at the moment.
I see that I now get jobs started at gitlab.com, but they fail because
BUILDENV_NATIVE_IMAGE: nettle/build-images:buildenv-native
image: $CI_REGISTRY/$BUILDENV_NATIVE_IMAGE
is expended to a reference that doesn't exist. It probably needs to point explicitly to the registry on git.lysator.liu.se (unless I move image building and hosting elsewhere).
And some of the jobs at git.lysator.liu.se picked up by your runner appear to suffer from a similar 403 problem as interactive access,
ERROR: Job failed: prepare environment: waiting for pod running: pulling image "git.lysator.liu.se:5050/nettle/build-images:buildenv-native" for container build: image pull failed: Back-off pulling image "git.lysator.liu.se:5050/nettle/build-images:buildenv-native": ErrImagePull: Requesting bear token: invalid status code from registry 403 (Forbidden). Check https://docs.gitlab.com/runner/shells/#shell-profile-loading for more information
Weird, and I probably need some assistance from local sysadm.
Regards, /Nies