There was a spurious failure of the Richards benchmark in the CI. No such failure had been previously observed in many runs. The job log is attached [job_log](/uploads/de092059c7504c36e9b73073c68aa798/job_log) Seems to be quite a consistent failure ~~after !2736~~ when using the new runner on sal.