acassis commented on PR #3416:
URL: https://github.com/apache/nuttx-apps/pull/3416#issuecomment-3991955490

   > again fetch extract issue, failed ci task restarted.
   > 
   > ```
   > Configuration/Tool: nucleo-h743zi2/jumbo,CONFIG_ARM_TOOLCHAIN_CLANG
   > 2026-03-03 02:30:09
   > 
------------------------------------------------------------------------------------
   >   Cleaning...
   >   Configuring...
   >   Disabling CONFIG_ARM_TOOLCHAIN_GNU_EABI
   >   Enabling CONFIG_ARM_TOOLCHAIN_CLANG
   >   Building NuttX...
   > 
   > gzip: stdin: not in gzip format
   > tar: Child returned status 1
   > tar: Error is not recoverable: exiting now
   > make[1]: *** [littlefs/Make.defs:68: .littlefsunpack] Error 2
   > make[1]: Target 'context' not remade because of errors.
   > make: *** [tools/Unix.mk:467: fs/.context] Error 2
   >   % Total    % Received % Xferd  Average Speed   Time    Time     Time  
Current
   >                                  Dload  Upload   Total   Spent    Left  
Speed
   > 
   >   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--   
  0
   >   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--   
  0
   > 
   >   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--   
  0
   > 100  496k  100  496k    0     0  1088k      0 --:--:-- --:--:-- --:--:-- 
2139k
   > make: Target 'all' not remade because of errors.
   > /github/workspace/sources/nuttx/tools/testbuild.sh: line 385: 
/github/workspace/sources/nuttx/../nuttx/nuttx.manifest: No such file or 
directory
   >   [1/1] Normalize nucleo-h743zi2/jumbo
   > ```
   
   @cederom maybe it still an issue with Github, but eventually most (or even 
all) links we are using will fade out, this is why we need to have a mirror.


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