It looks like for whatever reason, scap clean isn't cleaning the deployment up fully. It seems to be leaving /srv/mediawiki-staging/php-[version]/cache/l10n on disk, with nothing in it
rm -rf php-1.XX.X-wmf.X is enough to manually clean up...
It looks like for whatever reason, scap clean isn't cleaning the deployment up fully. It seems to be leaving /srv/mediawiki-staging/php-[version]/cache/l10n on disk, with nothing in it
rm -rf php-1.XX.X-wmf.X is enough to manually clean up...
That'll happen when you do a --delete, i.e. the branch directory will sit there empty until then next scap sync is run.
This is happening because the scap clean script is deleting the directory in /srv/mediawiki-staging on the deployment host, then syncing to all the other hosts as mwdeploy; however, the php-[version]/cache/l10n directory is not empty and is ignored (T157030). Now we go back as a final step and delete the dangling directories, but we don't delete their parent.
We could probably fix this by shifting some steps around in scap clean.
Those directories were still in /srv/mediawiki-staging on the deployment host, hence reporting the bug based on the investigation for T205000: Too many versions of MW core on deploy1001
I think so, yeah. Didn't actually check the targets at the time, but the folders are definitely gone from /srv/mediawiki now too