From: "Girar awaiter (pav)" <girar-builder@altlinux.org>
To: Pavel Vasenkov <pav@altlinux.org>
Cc: girar-builder-p10@altlinux.org,
sisyphus-incominger@lists.altlinux.org,
girar-builder-p10@lists.altlinux.org
Subject: [#321602] p10 TESTED trinity.git=1.9-alt6
Date: Mon, 22 May 2023 08:37:18 +0000
Message-ID: <girar.task.321602.1.1@gyle.mskdc.altlinux.org> (raw)
https://git.altlinux.org/tasks/321602/logs/events.1.1.log
subtask name aarch64 armh i586 ppc64le x86_64
#100 trinity 1:21 2:40 46 1:41 43
2023-May-22 08:30:25 :: test-only task #321602 for p10 started by pav:
#100 build 1.9-alt6 from /gears/t/trinity.git fetched at 2023-May-22 08:30:07 from sisyphus
2023-May-22 08:30:27 :: [ppc64le] #100 trinity.git 1.9-alt6: build start
2023-May-22 08:30:27 :: [aarch64] #100 trinity.git 1.9-alt6: build start
2023-May-22 08:30:27 :: [x86_64] #100 trinity.git 1.9-alt6: build start
2023-May-22 08:30:27 :: [armh] #100 trinity.git 1.9-alt6: build start
2023-May-22 08:30:27 :: [i586] #100 trinity.git 1.9-alt6: build start
2023-May-22 08:31:10 :: [x86_64] #100 trinity.git 1.9-alt6: build OK
2023-May-22 08:31:13 :: [i586] #100 trinity.git 1.9-alt6: build OK
2023-May-22 08:31:48 :: [aarch64] #100 trinity.git 1.9-alt6: build OK
2023-May-22 08:32:08 :: [ppc64le] #100 trinity.git 1.9-alt6: build OK
2023-May-22 08:33:07 :: [armh] #100 trinity.git 1.9-alt6: build OK
2023-May-22 08:33:20 :: #100: trinity.git 1.9-alt6: build check OK
2023-May-22 08:33:22 :: build check OK
2023-May-22 08:33:25 :: noarch check OK
2023-May-22 08:33:27 :: plan: src +1 -1 =18070, aarch64 +2 -2 =30562, armh +2 -2 =28648, i586 +2 -2 =31062, ppc64le +2 -2 =30102, x86_64 +2 -2 =31852
#100 trinity 1.9-alt4 -> 1.9-alt6
Fri May 19 2023 Pavel Vasenkov <pav@altlinux> 1.9-alt6
- Fix removing depricated i810 definations
Mon Feb 27 2023 Artyom Bystrov <arbars@altlinux> 1.9-alt5
- Add patch to fix build
2023-May-22 08:34:06 :: patched apt indices
2023-May-22 08:34:18 :: created next repo
2023-May-22 08:34:25 :: duplicate provides check OK
2023-May-22 08:34:59 :: dependencies check OK
2023-May-22 08:35:23 :: [x86_64 i586 aarch64 ppc64le armh] ELF symbols check OK
2023-May-22 08:35:38 :: [x86_64] #100 trinity: install check OK
2023-May-22 08:35:38 :: [i586] #100 trinity: install check OK
2023-May-22 08:35:45 :: [x86_64] #100 trinity-debuginfo: install check OK
2023-May-22 08:35:46 :: [i586] #100 trinity-debuginfo: install check OK
2023-May-22 08:35:48 :: [aarch64] #100 trinity: install check OK
2023-May-22 08:35:53 :: [ppc64le] #100 trinity: install check OK
2023-May-22 08:36:01 :: [aarch64] #100 trinity-debuginfo: install check OK
2023-May-22 08:36:06 :: [armh] #100 trinity: install check OK
2023-May-22 08:36:08 :: [ppc64le] #100 trinity-debuginfo: install check OK
2023-May-22 08:36:31 :: [armh] #100 trinity-debuginfo: install check OK
2023-May-22 08:36:47 :: [x86_64-i586] generated apt indices
2023-May-22 08:36:47 :: [x86_64-i586] created next repo
2023-May-22 08:36:56 :: [x86_64-i586] dependencies check OK
2023-May-22 08:36:58 :: gears inheritance check OK
2023-May-22 08:36:58 :: srpm inheritance check OK
girar-check-perms: access to trinity DENIED for pav: project `trinity' is not listed in the acl file for repository `p10', and the policy for such projects in `p10' is to deny
check-subtask-perms: #100: trinity: needs approvals from members of @maint and @tester groups
2023-May-22 08:37:00 :: acl check IGNORED
2023-May-22 08:37:08 :: created contents_index files
2023-May-22 08:37:16 :: created hash files: aarch64 armh i586 ppc64le src x86_64
2023-May-22 08:37:18 :: task #321602 for p10 TESTED
next reply other threads:[~2023-05-22 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 8:37 Girar awaiter (pav) [this message]
2023-05-22 11:09 ` [#321602] p10 EPERM (try 2) trinity.git=1.9-alt6 Girar awaiter (pav)
2023-06-06 17:00 ` [#321602] p10 DONE (try 3) trinity.git=1.9-alt6 Girar pender (amakeenk)
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.321602.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=pav@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