Skip to content

builds which run longer than 1h are terminating due to runner timeout

https://gitlab.archlinux.org/packaging-buildbtw-dev/packages/linux/-/jobs/374712

  CC [M]  fs/cachefiles/security.o
  CC [M]  fs/cachefiles/volume.o
  CC [M]  fs/cachefiles/xattr.o
  CC [M]  fs/cachefiles/ondemand.o
  LD [M]  fs/cachefiles/cachefiles.o
  CC [M]  fs/ocfs2/alloc.o
  CC [M]  fs/ocfs2/aops.o
  CC [M]  fs/ocfs2/blockcheck.o
  CC [M]  fs/ocfs2/buffer_head_io.o
  CC [M]  fs/ocfs2/dcache.o
  CC [M]  fs/ocfs2/dir.o
WARNING: step_script could not run to completion because the timeout was exceeded. For more control over job and script timeouts see: https://docs.gitlab.com/ci/runners/configure_runners/#set-script-and-after_script-timeouts
ERROR: Job failed: execution took longer than 1h0m0s seconds

I think in the long run with the goal of collecting more metrics for how builds usually take this can be reasonably set for each build job but initially it would be good to disable it as we don't know how long builds can take (especially on the small poc box) 😅

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information