I had a similar issue when simplifying the way we publish documentation ( e9de35e88f7a01e6abb72bde53a5c9d316838276 ). The issue is rsync --archive attempts to preserve time and permissions, hence why we get the warning. From the fix I did for doc:

# We do not --archive which preserves date, time or permissions.
# The base directory (such as ./cover) might have been populated by
# puppet and thus owned by a different user than rsyncd.
rsync --verbose --recursive --relative "${WMF_CI_PUB_DEST}" rsync://doc1001.eqiad.wmnet/doc/

Or in short, we need to drop --archive from the castor load command.

From another comment I made:

The cache is populated by rsync which is run inside a container and uses the 'nobody' user. However the /cache/ directory is owned by root iirc and thus rsync can not update the timestamps on the directory. Hence:

rsync: failed to set times on "/cache/.": Operation not permitted (1)

That is a non fatal error and can be ignored. It is due to rsync using --archive which implies --times and that option is used to optimize the transfer by comparing timestamps and avoid rsyncing files that have not been changed. Though, the cache is initially empty so we could probably drop that --times option. There is also --omit-dir-times

Hello, this issue seems to be blocking Wikibase CI now: https://integration.wikimedia.org/ci/job/mwgate-node18-docker/3936/console

In T188488#9475158, @Muhammad_Yasser_Jazirahly_WMDE wrote:

Hello, this issue seems to be blocking Wikibase CI now: https://integration.wikimedia.org/ci/job/mwgate-node18-docker/3936/console

This issue T188488 is about rsync spurting an error message which is otherwise ignored. The npm cache being corrupted is T295351 and I will clean it up:)