driazati commented on issue #11688:
URL: https://github.com/apache/tvm/issues/11688#issuecomment-1185901353

   The docker build passed, but it looks like [the validate 
failed](https://ci.tlcpack.ai/job/docker-images-ci/job/daily-docker-image-validate/),
 something between commits cf15375e2 and ca88c522f is causing this error on the 
QEMU build:
   
   ```
   [2022-07-15T18:49:46.656Z] INFO:__main__:b'[100%] [QEMU] CPU: riscv32\n'
   [2022-07-15T18:49:46.656Z] qemu-system-riscv32: error while loading shared 
libraries: libsnappy.so.1: cannot open shared object file: No such file or 
directory
   [2022-07-15T18:49:46.656Z] make[3]: *** [zephyr/CMakeFiles/run] Error 127
   [2022-07-15T18:49:46.656Z] 
INFO:__main__:b"zephyr/CMakeFiles/run.dir/build.make:70: recipe for target 
'zephyr/CMakeFiles/run' failed\n"
   [2022-07-15T18:49:46.656Z] make[2]: *** [zephyr/CMakeFiles/run.dir/all] 
Error 2
   [2022-07-15T18:49:46.656Z] INFO:__main__:b"CMakeFiles/Makefile2:2689: recipe 
for target 'zephyr/CMakeFiles/run.dir/all' failed\n"
   [2022-07-15T18:49:46.656Z] make[1]: *** [zephyr/CMakeFiles/run.dir/rule] 
Error 2
   [2022-07-15T18:49:46.656Z] INFO:__main__:b"CMakeFiles/Makefile2:2696: recipe 
for target 'zephyr/CMakeFiles/run.dir/rule' failed\n"
   [2022-07-15T18:49:46.656Z] make: *** [run] Error 2
   [2022-07-15T18:49:46.656Z] INFO:__main__:b"Makefile:527: recipe for target 
'run' failed\n"
   [2022-07-15T20:35:49.431Z] Sending interrupt signal to process
   [2022-07-15T20:35:49.756Z] Sending interrupt signal to process
   [2022-07-15T20:35:56.719Z] script returned exit code 143
   ```
    and for some reason the job doesn't exit but sits there until it hits the 3 
hr timeout. #11689 is the only change to the `docker/` folder in that range but 
it could be other code changes or even unpinned dependencies updating
   
   


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