Over the last couple weeks or so, I'm noticing relatively many instances where the post-build steps will change the status of an otherwise successful build to failure, for no apparent reason. Some examples:
- https://integration.wikimedia.org/ci/job/quibble-apitests-only-vendor-php83/12947/console
- https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php83-phpunit-standalone/3618/console
- https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php83-selenium/25823/console
They're all like:
+ exec docker run --entrypoint=bash --volume /srv/jenkins/workspace/quibble-apitests-only-vendor-php83/src:/src --volume /srv/jenkins/workspace/quibble-apitests-only-vendor-php83/cache:/cache --volume /srv/jenkins/workspace/quibble-apitests-only-vendor-php83/log:/log --security-opt seccomp=unconfined --init --rm --label jenkins.job=quibble-apitests-only-vendor-php83 --label jenkins.build=12947 --env-file /dev/fd/63 docker-registry.wikimedia.org/releng/quibble-bullseye-php83:1.16.0 -c '([[ "$ZUUL_PIPELINE" =~ ^(gate-and-submit|postmerge) ]] && npm cache verify) || :' ++ set +x [PostBuildScript] - [INFO] Executing post build scripts. Waiting for the completion of castor-save-workspace-cache Build step 'Execute scripts' changed build result to FAILURE Build step 'Execute scripts' marked build as failure