From: Girar Builder awaiter robot <girar-builder@altlinux.org> To: "Sergey V. Turchin" <zerg@altlinux.org> Cc: sisyphus-incominger@lists.altlinux.org, girar-builder-p9@altlinux.org Subject: [#249118] p9 EPERM kde5-ktp-contact-runner.git=19.12.3-alt2 Date: Wed, 1 Apr 2020 13:36:38 +0000 Message-ID: <20200401133637.GA17124@gyle.altlinux.org> (raw) http://git.altlinux.org/tasks/249118/logs/events.1.1.log 2020-Apr-01 13:25:00 :: task #249118 for p9 started by zerg: 2020-Apr-01 13:25:00 :: message: improve #100 build 19.12.3-alt2 from /people/zerg/packages/kde5-ktp-contact-runner.git fetched at 2020-Apr-01 13:06:51 ssh: connect to host epyc0.mskdc.altlinux.org port 222: No buffer space available 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: No buffer space available 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 epyc2.mskdc.altlinux.org port 222: No buffer space available 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 shaitan.mskdc.altlinux.org port 222: No buffer space available 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: No buffer space available ssh: connect to host epyc0.mskdc.altlinux.org port 222: No buffer space available rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.3] 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 shaitan.mskdc.altlinux.org port 222: No buffer space available 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: No buffer space available 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 shaitan.mskdc.altlinux.org port 222: No buffer space available 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 epyc0.mskdc.altlinux.org port 222: No buffer space available 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: No buffer space available ssh: connect to host shaitan.mskdc.altlinux.org port 222: No buffer space available rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.3] rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.3] 2020-Apr-01 13:25:05 :: [i586] #100 kde5-ktp-contact-runner.git 19.12.3-alt2: build start 2020-Apr-01 13:25:05 :: [aarch64] #100 kde5-ktp-contact-runner.git 19.12.3-alt2: build start 2020-Apr-01 13:25:05 :: [ppc64le] #100 kde5-ktp-contact-runner.git 19.12.3-alt2: build start 2020-Apr-01 13:25:05 :: [x86_64] #100 kde5-ktp-contact-runner.git 19.12.3-alt2: build start 2020-Apr-01 13:26:32 :: [x86_64] #100 kde5-ktp-contact-runner.git 19.12.3-alt2: build OK 2020-Apr-01 13:26:33 :: [aarch64] #100 kde5-ktp-contact-runner.git 19.12.3-alt2: build OK 2020-Apr-01 13:26:45 :: [ppc64le] #100 kde5-ktp-contact-runner.git 19.12.3-alt2: build OK 2020-Apr-01 13:26:55 :: [i586] #100 kde5-ktp-contact-runner.git 19.12.3-alt2: build OK 2020-Apr-01 13:27:21 :: #100: kde5-ktp-contact-runner.git 19.12.3-alt2: build check OK 2020-Apr-01 13:27:22 :: build check OK 2020-Apr-01 13:27:25 :: noarch check OK 2020-Apr-01 13:27:28 :: plan: src +1 -1 =17883, aarch64 +2 -2 =29821, i586 +2 -2 =32028, ppc64le +2 -2 =30160, x86_64 +2 -2 =32334 2020-Apr-01 13:27:28 :: version check OK #100 kde5-ktp-contact-runner 19.12.3-alt1 -> 19.12.3-alt2 Wed Apr 01 2020 Sergey V Turchin <zerg@altlinux> 19.12.3-alt2 - turn off krunner plugin by default 2020-Apr-01 13:28:43 :: generated apt indices 2020-Apr-01 13:28:43 :: created next repo 2020-Apr-01 13:29:46 :: dependencies check OK 2020-Apr-01 13:32:53 :: [x86_64 i586 aarch64 ppc64le] ELF symbols check OK 2020-Apr-01 13:33:28 :: [x86_64] #100 kde5-ktp-contact-runner: install check OK 2020-Apr-01 13:33:30 :: [i586] #100 kde5-ktp-contact-runner: install check OK 2020-Apr-01 13:35:20 :: [x86_64] #100 kde5-ktp-contact-runner-debuginfo: install check OK 2020-Apr-01 13:35:47 :: [i586] #100 kde5-ktp-contact-runner-debuginfo: install check OK 2020-Apr-01 13:35:51 :: [x86_64-i586] plan: #1 +1 -1 =10630 2020-Apr-01 13:36:07 :: [x86_64-i586] arepo build OK 2020-Apr-01 13:36:27 :: [x86_64-i586] generated apt indices 2020-Apr-01 13:36:27 :: [x86_64-i586] created next repo 2020-Apr-01 13:36:36 :: [x86_64-i586] dependencies check OK 2020-Apr-01 13:36:36 :: gears inheritance check OK 2020-Apr-01 13:36:36 :: srpm inheritance check OK girar-check-perms: access to @maint ALLOWED for zerg: member of approved group check-subtask-perms: #100: kde5-ktp-contact-runner: allowed for zerg, needs an approval from a member of @tester group 2020-Apr-01 13:36:37 :: acl check FAILED 2020-Apr-01 13:36:37 :: task #249118 for p9 EPERM
reply other threads:[~2020-04-01 13:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200401133637.GA17124@gyle.altlinux.org \ --to=girar-builder@altlinux.org \ --cc=girar-builder-p9@altlinux.org \ --cc=sisyphus-incominger@lists.altlinux.org \ --cc=zerg@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