The post-merge build i s currently failing (see e.g. this) as a result of the repo running the tox-py27-coverage-publish job.
Since we've updated to py37 this job should be updated to reflect this.
Per zuul/layout.yaml we are the only ones using this job so it should be safe to replace it in jjb/python-jobs.yaml and then point zuul/layout.yaml to the new one.
@JeanFred The syntax here is a bit outside of my comfort zone. Would you mind taking a look?
Thanks for filing this task @Lokal_Profil − that was on my todo :)
I was looking at this yesterday − I must have been tired as I did not connect the dots with the Py2 → py3 upgrade… will try that.
Change 827997 had a related patch set uploaded (by Jean-Frédéric; author: Jean-Frédéric):
[integration/config@master] Upgrade `tox-py[2|3]7-coverage-publish` to use python 3
Change 827997 merged by jenkins-bot:
[integration/config@master] jjb: Define `tox-py37-coverage-publish` to replace tox-py27-coverage-publish
Mentioned in SAL (#wikimedia-releng) [2022-08-30T16:00:12Z] <James_F> Zuul: [labs/tools/heritage] Switch postmerge job to tox-py37-coverage-publish for T316627
Looks like it is still failing. Below should be the cause (from this)
08:15:39 + exec docker run --entrypoint=/usr/bin/cobertura-clover-transform --volume /srv/jenkins/workspace/tox-py37-coverage-publish/src:/src --volume /srv/jenkins/workspace/tox-py37-coverage-publish/cache:/cache --volume /srv/jenkins/workspace/tox-py37-coverage-publish/log:/log --security-opt seccomp=unconfined --init --rm --label jenkins.job=tox-py37-coverage-publish --label jenkins.build=1 --env-file /dev/fd/63 docker-registry.wikimedia.org/releng/tox-buster:0.5.3 /log/coverage.xml -o /log/clover.xml 08:15:39 ++ /usr/bin/env 08:15:39 ++ egrep -v '^(HOME|SHELL|PATH|LOGNAME|MAIL)=' 08:15:39 [FATAL tini (7)] exec /usr/bin/cobertura-clover-transform failed: Permission denied 08:15:40 Build step 'Execute shell' marked build as failure