yamt commented on PR #14388: URL: https://github.com/apache/nuttx/pull/14388#issuecomment-2421633061
> These Timeout Errors will cost us precious GitHub Minutes. The remaining jobs get killed, and restarting these remaining jobs from scratch will consume extra GitHub Minutes. (1) How do we retry these Timeout Errors? (2) Can we have Restartable Builds? Doesn't quite make sense to build everything from scratch (arm6, arm7, riscv7) just because one job failed (xtensa2) (3) Or xtensa2 should wait for others to finish, before it declares a timeout and dies? Hmmm... > > ``` > Configuration/Tool: esp32s2-kaluga-1/lvgl_st7789 > curl: (28) Failed to connect to github.com port 443 after 133994 ms: Connection timed out > ``` > > https://github.com/apache/nuttx/actions/runs/11395811301/attempts/1 recent github allows us to restart only failed jobs. you don't need to restart everything. i suspect it isn't worth the effort to optimize it unless timeout errors are too frequent. (are they?) having said that, ideally, we should not use network during a build. it's simpler to fetch everything needed before starting the rest of build processes. such a mechanism would help users in a restricted environment, not only the CI. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
