ALT Linux Girar Builder robot reports
 help / color / mirror / Atom feed
From: "Girar awaiter (mike)" <girar-builder@altlinux.org>
To: Michael Shigorin <mike@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org,
	girar-builder-sisyphus@altlinux.org
Subject: [#371137] [test-only] FAILED (try 8) vtk.git=9.3.0-alt1.3 gdcm.git=3.0.24-alt2 freecad.git=1.0.0-alt1.1 ...
Date: Wed, 29 Jan 2025 10:11:18 +0000
Message-ID: <girar.task.371137.8.1@gyle.mskdc.altlinux.org> (raw)
In-Reply-To: <girar.task.371137.1.1@gyle.mskdc.altlinux.org>

https://git.altlinux.org/tasks/371137/logs/events.8.1.log
https://packages.altlinux.org/tasks/371137

2025-Jan-29 07:18:21 :: test-only task #371137 for sisyphus resumed by mike:
2025-Jan-29 07:18:21 :: message: testing client builds after libvtk split-up
#100 removed
#200 removed
#300 removed
#400 removed
#440 build 9.3.0-alt1.3 from /people/mike/packages/vtk.git fetched at 2025-Jan-29 00:11:37
#500 removed
#600 build 3.0.24-alt2 from /gears/g/gdcm.git fetched at 2025-Jan-29 07:17:14 from sisyphus
#700 build 1.0.0-alt1.1 from /gears/f/freecad.git fetched at 2025-Jan-29 07:17:28 from sisyphus
#1000 build 5.6.2-alt2 from /gears/s/slicer.git fetched at 2025-Jan-29 07:17:32 from sisyphus
2025-Jan-29 07:18:22 :: created build repo
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]
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 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]
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]
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]
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]
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 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 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]
[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 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 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
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]
/usr/libexec/girar-builder/gb-task-setup-remote-arch: line 22: 3141926 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 #371137 for sisyphus FAILED


  parent reply	other threads:[~2025-01-29 10:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 22:00 [#371137] TESTED vtk.git=9.3.0-alt1.3 Girar awaiter (mike)
2025-01-27 11:38 ` [#371137] TESTED (try 2) vtk.git=9.3.0-alt1.3 Girar awaiter (mike)
2025-01-28  0:50 ` [#371137] TESTED (try 3) vtk.git=9.3.0-alt1.3 Girar awaiter (mike)
2025-01-28  6:03 ` [#371137] FAILED (try 4) vtk.git=9.3.0-alt1.3 Girar awaiter (mike)
2025-01-28 10:52 ` [#371137] [test-only] FAILED (try 5) vtk.git=9.3.0-alt1.3 Girar awaiter (mike)
2025-01-28 13:07 ` [#371137] [test-only] FAILED (try 6) vtk.git=9.3.0-alt1.3 Girar awaiter (mike)
2025-01-29  2:52 ` [#371137] TESTED (try 7) vtk.git=9.3.0-alt1.3 Girar awaiter (mike)
2025-01-29 10:11 ` Girar awaiter (mike) [this message]
2025-01-29 14:54 ` [#371137] TESTED (try 9) vtk.git=9.3.0-alt1.3 gdcm.git=3.0.24-alt2 freecad.git=1.0.0-alt1.1 Girar awaiter (mike)

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.371137.8.1@gyle.mskdc.altlinux.org \
    --to=girar-builder@altlinux.org \
    --cc=devel@lists.altlinux.org \
    --cc=girar-builder-sisyphus@altlinux.org \
    --cc=mike@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