From: "Girar awaiter (lepata)" <girar-builder@altlinux.org>
To: Elena Mishina <lepata@altlinux.org>
Cc: girar-builder-p10@altlinux.org,
sisyphus-incominger@lists.altlinux.org,
girar-builder-p10@lists.altlinux.org
Subject: [#371906] p10 FAILED docs.git=docs-alt-education/10.4-alt2
Date: Wed, 29 Jan 2025 10:11:18 +0000
Message-ID: <girar.task.371906.1.1@gyle.mskdc.altlinux.org> (raw)
https://git.altlinux.org/tasks/371906/logs/events.1.1.log
https://packages.altlinux.org/tasks/371906
2025-Jan-29 08:34:53 :: task #371906 for p10 started by lepata:
2025-Jan-29 08:34:53 :: message: update_docs
#100 build docs-alt-education/10.4-alt2 from /people/lepata/packages/docs.git fetched at 2025-Jan-27 18:02:30
ssh: connect to host briareos.mskdc.altlinux.org port 222: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.3]
ssh: connect to host briareos.mskdc.altlinux.org port 222: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.3]
ssh: connect to host briareos.mskdc.altlinux.org port 222: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.3]
ssh: connect to host briareos.mskdc.altlinux.org port 222: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.3]
[sender] io timeout after 300 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
[sender] io timeout after 300 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
[sender] io timeout after 301 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
[sender] io timeout after 300 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
[sender] io timeout after 301 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
[sender] io timeout after 300 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
ssh: mux_client_request_session: read from master failed: Broken pipe
[sender] io timeout after 301 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
ssh: connect to host briareos.mskdc.altlinux.org port 222: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.3]
[sender] io timeout after 301 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
[sender] io timeout after 300 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
[sender] io timeout after 301 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
[sender] io timeout after 300 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
[sender] io timeout after 300 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
[sender] io timeout after 301 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
ssh: mux_client_request_session: read from master failed: Broken pipe
[sender] io timeout after 300 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(195) [sender=3.1.3]
/usr/libexec/girar-builder/gb-task-setup-remote-arch: line 22: 3581543 Terminated gb-x-rsync-loop -a "$GB_HOME/remote/" "$remote_host:"
2025-Jan-29 10:11:16 :: [ppc64le] requesting cancellation of task processing
2025-Jan-29 10:11:16 :: [ppc64le] setup-remote FAILED
2025-Jan-29 10:11:17 :: task #371906 for p10 FAILED
next reply other threads:[~2025-01-29 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 10:11 Girar awaiter (lepata) [this message]
2025-01-29 13:59 ` [#371906] p10 EPERM (try 2) docs.git=docs-alt-education/10.4-alt2 Girar awaiter (lepata)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=girar.task.371906.1.1@gyle.mskdc.altlinux.org \
--to=girar-builder@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=girar-builder-p10@altlinux.org \
--cc=girar-builder-p10@lists.altlinux.org \
--cc=lepata@altlinux.org \
--cc=sisyphus-incominger@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Girar Builder robot reports
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus-incominger/0 sisyphus-incominger/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 sisyphus-incominger sisyphus-incominger/ http://lore.altlinux.org/sisyphus-incominger \
sisyphus-incominger@lists.altlinux.org sisyphus-incominger@lists.altlinux.ru sisyphus-incominger@lists.altlinux.com
public-inbox-index sisyphus-incominger
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus-incominger
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git