tmedicci commented on issue #15730: URL: https://github.com/apache/nuttx/issues/15730#issuecomment-2675439727
I had an idea to keep improving our CI (and lower our GitHub runners usage). Nowadays, we have a set of rules to build parallel jobs for specific target groups. Each target group usually contains jobs for the same _arch_ (usually, sub-grouped by _chip_). Instead of running these parallel jobs, what do you think about building only the `citest` defconfig for every eligible arch and making this a necessary step to run the other defconfigs? We have previously talked about providing a `citest` (or `ostest`, or `hwtest`: a config that enables most of the features and make it more suitable for testing on CI) for every supported board. By running this defconfig (for all eligible archs), we can avoid running the other parallel jobs for every single `defconfig` if the most basic (`citest`) fails. @lupyuen , have you already tested something similar? -- 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
