casaroli commented on PR #3685: URL: https://github.com/apache/nuttx-apps/pull/3685#issuecomment-5287289240
I believe the best option is to partition CI into more granular checks. We already split by arch, but I think we can go further and split by config: compute the blast radius of a change and rebuild/test only the configs it actually affects. It is a lot of engineering, but I believe it is worth it, since it could cut GitHub Actions consumption considerably. I am not sure what the ultimate benefit would be, but it is probably worth measuring. I am still not sure whether we can use ccache: that could be a short-term improvement. The alternative is fixing the build system so it can reuse artifacts from previous builds instead of requiring a distclean every time. I think all of this is possible, and all of it is worth a measurement. IMHO what we cannot afford is buying back a few KB every time this platform goes over the limit — for a platform nobody uses, kept only because it is our single config that we can test under QEMU. So either we trim it properly (i.e. remove networking and telnet), or we drop it entirely: protected build is not feasible on that tiva board. WDYT? -- 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]
