coverage jobs sometimes exceed maximum execution time
@adam-mercer @duncanmmacleod now and then I see the coverage
job in the integration
step of the CI pipeline fail with: The script exceeded the maximum execution time set for the job
. Examples here and here; specifically that limit seems to be ERROR: Job failed: execution took longer than 1h0m0s seconds
.
Is that just something we have to live with during busy times of the system, or do you have some hunch where it may be slowing down specifically? I'd say just increasing the limit is not a good option, as one hour already seems quite generous.