[riscv-reports] [#138033] sisyphus_riscv64 FAILED srpm=vtk-9.5.2-alt5.src.rpm

Girar sisyphus_riscv64 awaiter iv noreply at basealt.ru
Fri Aug 21 21:58:09 MSK 2026


http://web.build.srt.basealt.ru/tasks/138033/logs/events.1.1.log

subtask  name  riscv64
   #100  vtk    failed

2026-Aug-21 18:54:13 :: task #138033 for sisyphus_riscv64 started by iv:
2026-Aug-21 18:54:13 :: message: sync
#100 build vtk-9.5.2-alt5.src.rpm
2026-Aug-21 18:54:16 :: [riscv64] #100 vtk-9.5.2-alt5.src.rpm: build start
Timeout, server 10.64.20.41 not responding.
ssh: connect to host 10.64.20.41 port 22: No route to host
2026-Aug-21 18:56:51 :: [riscv64] #100 vtk-9.5.2-alt5.src.rpm: build FAILED
2026-Aug-21 18:56:51 :: [riscv64] requesting cancellation of task processing
ssh: connect to host 10.64.20.41 port 22: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
ssh: connect to host 10.64.20.41 port 22: No route to host
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(232) [Receiver=3.2.7]
2026-Aug-21 18:58:09 :: [riscv64] build FAILED
2026-Aug-21 18:58:09 :: task #138033 for sisyphus_riscv64 FAILED


More information about the Riscv-reports mailing list