From: "Girar awaiter (thatman)" <girar-builder@altlinux.org> To: Alexander Burmatov <thatman@altlinux.org> Cc: sisyphus-incominger@lists.altlinux.org, girar-builder-sisyphus@altlinux.org Subject: [#314373] FAILED (try 3) cargo-make.git=0.36.4-alt1 Date: Mon, 27 Feb 2023 14:22:02 +0000 Message-ID: <girar.task.314373.3.1@gyle.mskdc.altlinux.org> (raw) In-Reply-To: <girar.task.314373.1.1@gyle.mskdc.altlinux.org> https://git.altlinux.org/tasks/314373/logs/events.3.1.log subtask name aarch64 armh i586 ppc64le x86_64 #200 cargo-make failed failed failed failed failed 2023-Feb-27 14:20:55 :: task #314373 for sisyphus resumed by thatman: #100 removed #200 build 0.36.4-alt1 from /people/thatman/packages/cargo-make.git fetched at 2023-Feb-27 14:20:34 2023-Feb-27 14:20:57 :: [x86_64] #200 cargo-make.git 0.36.4-alt1: build start 2023-Feb-27 14:20:57 :: [armh] #200 cargo-make.git 0.36.4-alt1: build start 2023-Feb-27 14:20:57 :: [aarch64] #200 cargo-make.git 0.36.4-alt1: build start 2023-Feb-27 14:20:57 :: [i586] #200 cargo-make.git 0.36.4-alt1: build start 2023-Feb-27 14:20:57 :: [ppc64le] #200 cargo-make.git 0.36.4-alt1: build start [x86_64] + cargo build --release -j32 --offline [x86_64] error: no matching package named `cargo_metadata` found [x86_64] location searched: registry `crates-io` 2023-Feb-27 14:21:17 :: [x86_64] cargo-make.git 0.36.4-alt1: remote: build failed 2023-Feb-27 14:21:17 :: [x86_64] #200 cargo-make.git 0.36.4-alt1: build FAILED 2023-Feb-27 14:21:17 :: [x86_64] requesting cancellation of task processing [i586] + cargo build --release -j32 --offline [i586] error: no matching package named `cargo_metadata` found [i586] location searched: registry `crates-io` 2023-Feb-27 14:21:20 :: [i586] cargo-make.git 0.36.4-alt1: remote: build failed 2023-Feb-27 14:21:20 :: [i586] #200 cargo-make.git 0.36.4-alt1: build FAILED [ppc64le] + cargo build --release -j43 --offline --no-default-features --features=tls-native [ppc64le] error: no matching package named `cargo_metadata` found [ppc64le] location searched: registry `crates-io` 2023-Feb-27 14:21:47 :: [ppc64le] cargo-make.git 0.36.4-alt1: remote: build failed 2023-Feb-27 14:21:47 :: [ppc64le] #200 cargo-make.git 0.36.4-alt1: build FAILED [armh] + cargo build --release -j32 --offline [armh] error: no matching package named `cargo_metadata` found [armh] location searched: registry `crates-io` 2023-Feb-27 14:21:50 :: [armh] cargo-make.git 0.36.4-alt1: remote: build failed 2023-Feb-27 14:21:50 :: [armh] #200 cargo-make.git 0.36.4-alt1: build FAILED [aarch64] + cargo build --release -j24 --offline [aarch64] error: no matching package named `cargo_metadata` found [aarch64] location searched: registry `crates-io` 2023-Feb-27 14:22:02 :: [aarch64] cargo-make.git 0.36.4-alt1: remote: build failed 2023-Feb-27 14:22:02 :: [aarch64] #200 cargo-make.git 0.36.4-alt1: build FAILED 2023-Feb-27 14:21:17 :: [x86_64] build FAILED 2023-Feb-27 14:21:20 :: [i586] build FAILED 2023-Feb-27 14:21:48 :: [ppc64le] build FAILED 2023-Feb-27 14:21:51 :: [armh] build FAILED 2023-Feb-27 14:22:02 :: [aarch64] build FAILED 2023-Feb-27 14:22:02 :: task #314373 for sisyphus FAILED
next prev parent reply other threads:[~2023-02-27 14:22 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-30 13:03 [#314373] TESTED cargo-make.git=0.36.4-alt1 Girar awaiter (thatman) 2023-01-31 12:24 ` [#314373] EPERM (try 2) cargo-make.git=0.36.4-alt1 Girar awaiter (thatman) 2023-02-27 14:22 ` Girar awaiter (thatman) [this message] 2023-02-27 14:48 ` [#314373] EPERM (try 4) cargo-make.git=0.36.5-alt1 Girar awaiter (thatman) 2023-03-17 19:05 ` [#314373] DONE (try 5) cargo-make.git=0.36.5-alt1 Girar pender (thatman)
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.314373.3.1@gyle.mskdc.altlinux.org \ --to=girar-builder@altlinux.org \ --cc=devel@lists.altlinux.org \ --cc=girar-builder-sisyphus@altlinux.org \ --cc=sisyphus-incominger@lists.altlinux.org \ --cc=thatman@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