tmedicci commented on issue #15730: URL: https://github.com/apache/nuttx/issues/15730#issuecomment-2679052278
> The ones that already exist. It may take more time to build separate configurations, but there will be no additional burden and compatibility problems. Anyways, this idea is nice, but looks like we need some other stuff first, and we work in our free time surrounded with thousands of other tasks :\ > > [@lupyuen](https://github.com/lupyuen) already created some `test_xxx` configurations.. but after some considerations I feel like this is just additional work with not much benefit? Well, let's quantify it: there are **342** boards and **1654** defconfigs. It can be even less than that: consider testing only a single board for each chip, that would be less than **110** defconfigs. The idea is to test a single defconfig for each board (worst case) and, if successful, proceed to test the other defconfigs. Currently, our CI triggers up to 32 parallel jobs to build the 1654 defconfigs. If one of these jobs fails, the others will continue running. By running only a single job to build 110 defconfigs, we can stop as soon as the first build fails. This would save a lot of GH runners usage. I think it's a _huge_ benefit! -- 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
