[riscv-reports] [#103999] sisyphus_riscv64 FAILED srpm=cage-0.2.1-alt2.src.rpm
Girar sisyphus_riscv64 awaiter recycler
noreply at basealt.ru
Sun Dec 14 00:12:52 MSK 2025
http://web.build.srt.basealt.ru/tasks/103999/logs/events.1.1.log
subtask name riscv64
#100 cage failed
2025-Dec-13 21:08:06 :: shared task #103999 for sisyphus_riscv64 started by recycler:
2025-Dec-13 21:08:06 :: message: sync
#100 build cage-0.2.1-alt2.src.rpm
2025-Dec-13 21:08:15 :: [riscv64] #100 cage-0.2.1-alt2.src.rpm: build start
Timeout, server 10.64.20.42 not responding.
ssh: connect to host 10.64.20.42 port 22: No route to host
2025-Dec-13 21:10:50 :: [riscv64] #100 cage-0.2.1-alt2.src.rpm: build FAILED
2025-Dec-13 21:10:50 :: [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: 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: 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: 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: 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]
2025-Dec-13 21:12:52 :: [riscv64] build FAILED
2025-Dec-13 21:12:52 :: task #103999 for sisyphus_riscv64 FAILED
More information about the Riscv-reports
mailing list