csanchezdll commented on PR #18549:
URL: https://github.com/apache/nuttx/pull/18549#issuecomment-4088604111

   It seems the checks failed for external reasons:
   ```
   2026-03-18T17:08:37.0961786Z 
====================================================================================
   2026-03-18T17:08:37.0985532Z Cmake in present: 
nrf52832-dk/sdc_nimble,CONFIG_ARM_TOOLCHAIN_GNU_EABI
   2026-03-18T17:08:37.0986163Z Configuration/Tool: 
nrf52832-dk/sdc_nimble,CONFIG_ARM_TOOLCHAIN_GNU_EABI
   2026-03-18T17:08:37.1082281Z 2026-03-18 17:08:37
   2026-03-18T17:08:37.1082912Z 
------------------------------------------------------------------------------------
   2026-03-18T17:08:37.1083565Z   Cleaning...
   2026-03-18T17:08:37.1083912Z   Configuring...
   2026-03-18T17:08:40.6514312Z   Select HOST_LINUX=y
   2026-03-18T17:08:42.4686084Z    TOOLS_DIR path is 
"/github/workspace/sources/nuttx"
   2026-03-18T17:08:42.4686690Z    HOST = Linux
   2026-03-18T17:09:12.8302758Z CMake Error at 
/github/workspace/sources/nuttx/build/_deps/sdk-nrfxlib-subbuild/sdk-nrfxlib-populate-prefix/src/sdk-nrfxlib-populate-stamp/download-sdk-nrfxlib-populate.cmake:170
 (message):
   2026-03-18T17:09:12.8305413Z   Each download failed!
   2026-03-18T17:09:12.8305662Z 
   2026-03-18T17:09:12.8306251Z     error: downloading 
'https://github.com/nrfconnect/sdk-nrfxlib/archive/v2.3.0.tar.gz' failed
   2026-03-18T17:09:12.8307418Z           status_code: 28
   2026-03-18T17:09:12.8307887Z           status_string: "Timeout was reached"
   ```
   I have checked other runs of the same build job Linux (arm-05) on other PRs 
and it runs well, so I guess this is a transient error.
   I am re-pushing to force a re-run (maybe admins can trigger a run on this 
job only, but I can not).


-- 
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]

Reply via email to