lupyuen commented on issue #15451: URL: https://github.com/apache/nuttx/issues/15451#issuecomment-2576576664
@simbit18 @raiden00pl @xiaoxiang781216 Yeah I [reported this earlier](https://github.com/apache/nuttx/pull/15413#issuecomment-2574336604) based on NuttX Dashboard, [and this also](https://github.com/apache/nuttx/pull/15425#issuecomment-2574214966). I'm kinda exhausted from monitoring our CI Jobs every day since November. And it's not sustainable (in case something happens to me). Let's do this:  - Remember that we agreed to halve the CI Jobs for Complex PRs? We did this to stay within the ASF Budget of 25 full-time GitHub Runners: https://lupyuen.org/articles/ci3.html - Over the past 30 days, we consumed 10 full-time runners (pic above) - The load was higher than usual, because we ran more CI Jobs for NuttX Release. (Merging a Release Branch will trigger 100% of CI Jobs) - This means we have spare capacity to double our CI Jobs. Thus we shall remove the 50% limit on CI Jobs for Complex PRs. Which means we shall run 100% of CI Jobs for Complex PRs. - Except we won't run risc-v-07, since it compiles CPython for NuttX and might exceed our budget. [(risc-v-07 will run in NuttX Build Farm instead)](https://github.com/apache/nuttx/pull/15099#issuecomment-2540355419) - When we receive complaints about overuse of GitHub Runners: I'll reduce the CI Jobs back to 50% - Hopefully this will improve the quality of Complex PRs, failing less often during the Daily Builds. I'm sorry Complex PRs will no longer complete CI Checks within 1.5 hours, they will now complete in 2 hours 10 mins. - I'll prepare the PR now to increase the CI Jobs. Thanks :-) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
