From: "Girar awaiter (fl0pp5)" <girar-builder@altlinux.org> To: Ivan Pepelyaev <fl0pp5@altlinux.org> Cc: sisyphus-incominger@lists.altlinux.org, girar-builder-sisyphus@altlinux.org Subject: [#335455] [test-only] FAILED (try 4) bbolt.git=1.3.8-alt1 trivy-db-utils.git=0.0.1-alt1 Date: Thu, 30 Nov 2023 17:10:33 +0000 Message-ID: <girar.task.335455.4.1@gyle.mskdc.altlinux.org> (raw) In-Reply-To: <girar.task.335455.1.1@gyle.mskdc.altlinux.org> https://git.altlinux.org/tasks/335455/logs/events.4.1.log subtask name aarch64 armh i586 ppc64le x86_64 #500 trivy-db-utils failed failed failed failed failed 2023-Nov-30 17:07:57 :: test-only task #335455 for sisyphus resumed by fl0pp5: #100 build 1.3.8-alt1 from /people/fl0pp5/packages/bbolt.git fetched at 2023-Nov-30 16:58:55 #200 removed #300 removed #400 removed #500 build 0.0.1-alt1 from /people/fl0pp5/packages/trivy-db-utils.git fetched at 2023-Nov-30 17:07:53 2023-Nov-30 17:07:58 :: created build repo 2023-Nov-30 17:08:00 :: [i586] #100 bbolt.git 1.3.8-alt1: build start 2023-Nov-30 17:08:00 :: [x86_64] #100 bbolt.git 1.3.8-alt1: build start 2023-Nov-30 17:08:00 :: [aarch64] #100 bbolt.git 1.3.8-alt1: build start 2023-Nov-30 17:08:00 :: [ppc64le] #100 bbolt.git 1.3.8-alt1: build start 2023-Nov-30 17:08:00 :: [armh] #100 bbolt.git 1.3.8-alt1: build start 2023-Nov-30 17:08:14 :: [i586] #100 bbolt.git 1.3.8-alt1: build OK (cached) 2023-Nov-30 17:08:14 :: [i586] #500 trivy-db-utils.git 0.0.1-alt1: build start 2023-Nov-30 17:08:14 :: [x86_64] #100 bbolt.git 1.3.8-alt1: build OK (cached) 2023-Nov-30 17:08:14 :: [x86_64] #500 trivy-db-utils.git 0.0.1-alt1: build start 2023-Nov-30 17:08:31 :: [aarch64] #100 bbolt.git 1.3.8-alt1: build OK (cached) 2023-Nov-30 17:08:31 :: [aarch64] #500 trivy-db-utils.git 0.0.1-alt1: build start 2023-Nov-30 17:08:39 :: [ppc64le] #100 bbolt.git 1.3.8-alt1: build OK (cached) 2023-Nov-30 17:08:40 :: [ppc64le] #500 trivy-db-utils.git 0.0.1-alt1: build start 2023-Nov-30 17:08:44 :: [armh] #100 bbolt.git 1.3.8-alt1: build OK (cached) 2023-Nov-30 17:08:44 :: [armh] #500 trivy-db-utils.git 0.0.1-alt1: build start [x86_64] Processing files: trivy-db-utils-0.0.1-alt1 [x86_64] error: No such file or directory: /usr/src/tmp/trivy-db-utils-buildroot/usr/bin/trivy-db-utils [x86_64] Executing(%doc): /bin/sh -e /usr/src/tmp/rpm-tmp.56331 [x86_64] -- [x86_64] RPM build errors: [x86_64] No such file or directory: /usr/src/tmp/trivy-db-utils-buildroot/usr/bin/trivy-db-utils 2023-Nov-30 17:08:50 :: [x86_64] trivy-db-utils.git 0.0.1-alt1: remote: build failed 2023-Nov-30 17:08:50 :: [x86_64] #500 trivy-db-utils.git 0.0.1-alt1: build FAILED 2023-Nov-30 17:08:50 :: [x86_64] requesting cancellation of task processing [i586] Processing files: trivy-db-utils-0.0.1-alt1 [i586] error: No such file or directory: /usr/src/tmp/trivy-db-utils-buildroot/usr/bin/trivy-db-utils [i586] Executing(%doc): /bin/sh -e /usr/src/tmp/rpm-tmp.36159 [i586] -- [i586] RPM build errors: [i586] No such file or directory: /usr/src/tmp/trivy-db-utils-buildroot/usr/bin/trivy-db-utils 2023-Nov-30 17:08:51 :: [i586] trivy-db-utils.git 0.0.1-alt1: remote: build failed 2023-Nov-30 17:08:51 :: [i586] #500 trivy-db-utils.git 0.0.1-alt1: build FAILED [aarch64] Processing files: trivy-db-utils-0.0.1-alt1 [aarch64] error: No such file or directory: /usr/src/tmp/trivy-db-utils-buildroot/usr/bin/trivy-db-utils [aarch64] Executing(%doc): /bin/sh -e /usr/src/tmp/rpm-tmp.28617 [aarch64] -- [aarch64] RPM build errors: [aarch64] No such file or directory: /usr/src/tmp/trivy-db-utils-buildroot/usr/bin/trivy-db-utils 2023-Nov-30 17:09:43 :: [aarch64] trivy-db-utils.git 0.0.1-alt1: remote: build failed 2023-Nov-30 17:09:43 :: [aarch64] #500 trivy-db-utils.git 0.0.1-alt1: build FAILED [ppc64le] Processing files: trivy-db-utils-0.0.1-alt1 [ppc64le] error: No such file or directory: /usr/src/tmp/trivy-db-utils-buildroot/usr/bin/trivy-db-utils [ppc64le] Executing(%doc): /bin/sh -e /usr/src/tmp/rpm-tmp.34366 [ppc64le] -- [ppc64le] RPM build errors: [ppc64le] No such file or directory: /usr/src/tmp/trivy-db-utils-buildroot/usr/bin/trivy-db-utils 2023-Nov-30 17:10:02 :: [ppc64le] trivy-db-utils.git 0.0.1-alt1: remote: build failed 2023-Nov-30 17:10:02 :: [ppc64le] #500 trivy-db-utils.git 0.0.1-alt1: build FAILED [armh] Processing files: trivy-db-utils-0.0.1-alt1 [armh] error: No such file or directory: /usr/src/tmp/trivy-db-utils-buildroot/usr/bin/trivy-db-utils [armh] Executing(%doc): /bin/sh -e /usr/src/tmp/rpm-tmp.71760 [armh] -- [armh] RPM build errors: [armh] No such file or directory: /usr/src/tmp/trivy-db-utils-buildroot/usr/bin/trivy-db-utils 2023-Nov-30 17:10:33 :: [armh] trivy-db-utils.git 0.0.1-alt1: remote: build failed 2023-Nov-30 17:10:33 :: [armh] #500 trivy-db-utils.git 0.0.1-alt1: build FAILED 2023-Nov-30 17:08:50 :: [x86_64] build FAILED 2023-Nov-30 17:08:51 :: [i586] build FAILED 2023-Nov-30 17:09:43 :: [aarch64] build FAILED 2023-Nov-30 17:10:02 :: [ppc64le] build FAILED 2023-Nov-30 17:10:33 :: [armh] build FAILED 2023-Nov-30 17:10:33 :: task #335455 for sisyphus FAILED
next prev parent reply other threads:[~2023-11-30 17:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-30 17:00 [#335455] [test-only] FAILED " Girar awaiter (fl0pp5) 2023-11-30 17:04 ` [#335455] [test-only] FAILED (try 2) " Girar awaiter (fl0pp5) 2023-11-30 17:07 ` [#335455] [test-only] FAILED (try 3) " Girar awaiter (fl0pp5) 2023-11-30 17:10 ` Girar awaiter (fl0pp5) [this message] 2023-11-30 17:16 ` [#335455] [test-only] FAILED (try 5) " Girar awaiter (fl0pp5) 2023-11-30 17:20 ` [#335455] [test-only] FAILED (try 6) " Girar awaiter (fl0pp5) 2023-11-30 17:28 ` [#335455] TESTED (try 7) " Girar awaiter (fl0pp5)
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.335455.4.1@gyle.mskdc.altlinux.org \ --to=girar-builder@altlinux.org \ --cc=devel@lists.altlinux.org \ --cc=fl0pp5@altlinux.org \ --cc=girar-builder-sisyphus@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