cederom commented on issue #17721: URL: https://github.com/apache/nuttx/issues/17721#issuecomment-3703764686
> Each new configuration added burdens CI because it must be built during testing. Adding separate configurations for simple programs doesn't make sense, especially when the target has a lot of flash and a single large configuration can be created (example: https://github.com/apache/nuttx/blob/master/boards/arm/stm32h7/nucleo-h743zi2/configs/jumbo/defconfig) Hmm, but this makes a lot of sense for NXDART that we are working on with @lupyuen - to have specific small configuration per device that is shared for all boards - then we can have nsh, ostest, coremark to verify build and basics, ostest, and possible performance regressions on a real world hardware boards. I know there are big devices that can have all this bundled, but this also makes scripting a bit harder because of "special cases" for different boards and not the same common setup for all boards. What solution can you see here @raiden00pl? It would be simpler to have specific configurations list for the CI build rather than making runtime testing a lot more complex? :-) -- 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]
