[riscv-reports] [#93175] sisyphus_riscv64 FAILED srpm=postgresql13-pgpool-II-4.6.3-alt1.src.rpm ...
Girar sisyphus_riscv64 awaiter recycler
noreply at basealt.ru
Wed Aug 27 08:16:27 MSK 2025
http://web.build.srt.basealt.ru/tasks/93175/logs/events.1.1.log
subtask name riscv64
#100 postgresql13-pgpool-II failed
2025-Aug-27 05:12:23 :: shared task #93175 for sisyphus_riscv64 started by recycler:
2025-Aug-27 05:12:23 :: message: sync
#100 build postgresql13-pgpool-II-4.6.3-alt1.src.rpm
#200 build postgresql14-pgpool-II-4.6.3-alt1.src.rpm
#300 build postgresql15-pgpool-II-4.6.3-alt1.src.rpm
#400 build postgresql16-pgpool-II-4.6.3-alt1.src.rpm
#500 build postgresql17-pgpool-II-4.6.3-alt1.src.rpm
2025-Aug-27 05:12:23 :: created build repo
2025-Aug-27 05:12:34 :: [riscv64] #100 postgresql13-pgpool-II-4.6.3-alt1.src.rpm: build start
Timeout, server 10.64.20.41 not responding.
ssh: connect to host 10.64.20.41 port 22: Connection timed out
2025-Aug-27 05:15:29 :: [riscv64] #100 postgresql13-pgpool-II-4.6.3-alt1.src.rpm: build FAILED
2025-Aug-27 05:15:29 :: [riscv64] requesting cancellation of task processing
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: 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: 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]
2025-Aug-27 05:16:27 :: [riscv64] build FAILED
2025-Aug-27 05:16:27 :: task #93175 for sisyphus_riscv64 FAILED
More information about the Riscv-reports
mailing list