fdcavalcanti commented on PR #18500: URL: https://github.com/apache/nuttx/pull/18500#issuecomment-4023223310
> I have a hunch about the ESP32 Download Failure: We are running too many jobs in parallel, which will fire Many Concurrent HTTP Requests to download the ESP32 Runtime (via github.com). And our Concurrent Downloads will get blocked by github.com for suspected spam. > > Maybe we should chat with our ESP32 Colleagues: Do they host the ESP32 Runtime outside of GitHub? Preferably on Multiple Hostnames, so we don't spam One Single Server? (Or can they offer to host ESP32 Runtime elsewhere?) > > Fixing the ESP32 Downloads is a terrific start. I see it failing all the time on NuttX Dashboard (sigh) You mean fix the ESP32 downloads inside the CI, right? I'm not sure how NuttX CI is dealing with it but the way to avoid this problem is simply use the `NXTMPDIR` option. It downloads the external dependency to `nuttx/../nxtmpdir' only once and reuses it on subsequent builds. That is how we use it internally: - Each board that we test divides the build stage in jobs like `a-f`, `g-l`, and so on. This gives us 4 build jobs per board. - Build jobs are "clean" when started. They required a complete fetch of the nuttx, nuttx-apps and hal repos. - Each build job, before starting, downloads those three repos and the HAL one is put inside nuttxspace/nxtmpdir/. - During each `make` command, we simply add the `NXTMPDIR=../nxtmpdir` environment flag to it. - Download once, build many times. -- 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]
