[riscv-reports] [#126645] sisyphus_riscv64 FAILED srpm=libowt-tg-4.3.0.15-alt1.src.rpm ...

[Girar sisyphus_riscv64 awaiter recycler]

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

subtask  name              riscv64
   #100  libowt-tg           26:57
   #200  telegram-desktop   failed

2026-May-24 20:14:11 :: shared task #126645 for sisyphus_riscv64 started by recycler:
2026-May-24 20:14:11 :: message: sync
#100 build libowt-tg-4.3.0.15-alt1.src.rpm
#200 build telegram-desktop-6.8.2-alt1.src.rpm
2026-May-24 20:14:11 :: created build repo
2026-May-24 20:14:17 :: [riscv64] #100 libowt-tg-4.3.0.15-alt1.src.rpm: build start
2026-May-24 20:41:14 :: [riscv64] #100 libowt-tg-4.3.0.15-alt1.src.rpm: build OK
2026-May-24 20:41:14 :: [riscv64] #200 telegram-desktop-6.8.2-alt1.src.rpm: build start
Timeout, server 10.64.20.42 not responding.
ssh: connect to host 10.64.20.42 port 22: Connection timed out
2026-May-24 21:47:27 :: [riscv64] #200 telegram-desktop-6.8.2-alt1.src.rpm: build FAILED
2026-May-24 21:47:27 :: [riscv64] requesting cancellation of task processing
ssh: connect to host 10.64.20.42 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.42 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.42 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.42 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.42 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.42 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.42 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.42 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.42 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.42 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.42 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.42 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-May-24 21:48:42 :: [riscv64] build FAILED
2026-May-24 21:48:42 :: task #126645 for sisyphus_riscv64 FAILED