From: "Girar awaiter (shaba)" <girar-builder@altlinux.org>
To: Alexey Shabalin <shaba@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org,
girar-builder-sisyphus@altlinux.org
Subject: [#349723] FAILED gitea-act.git=0.2.10-alt3
Date: Tue, 28 May 2024 13:39:55 +0000
Message-ID: <girar.task.349723.1.1@gyle.mskdc.altlinux.org> (raw)
https://git.altlinux.org/tasks/349723/logs/events.1.1.log
subtask name aarch64 i586 ppc64le x86_64
#100 gitea-act failed failed failed failed
2024-May-28 13:39:03 :: task #349723 for sisyphus started by shaba:
#100 build 0.2.10-alt3 from /people/shaba/packages/gitea-act.git fetched at 2024-May-28 13:39:01
2024-May-28 13:39:05 :: [aarch64] #100 gitea-act.git 0.2.10-alt3: build start
2024-May-28 13:39:05 :: [ppc64le] #100 gitea-act.git 0.2.10-alt3: build start
2024-May-28 13:39:05 :: [i586] #100 gitea-act.git 0.2.10-alt3: build start
2024-May-28 13:39:05 :: [x86_64] #100 gitea-act.git 0.2.10-alt3: build start
[x86_64] golang.org/x/crypto@v0.22.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[x86_64] golang.org/x/net@v0.24.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[x86_64] golang.org/x/sys@v0.19.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[x86_64] golang.org/x/crypto@v0.19.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[x86_64] golang.org/x/net@v0.21.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[x86_64] golang.org/x/sys@v0.18.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[x86_64] golang.org/x/term@v0.18.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[x86_64] To ignore the vendor directory, use -mod=readonly or -mod=mod.
[x86_64] To sync the vendor directory, run:
[x86_64] go mod vendor
2024-May-28 13:39:32 :: [x86_64] gitea-act.git 0.2.10-alt3: remote: build failed
2024-May-28 13:39:32 :: [x86_64] #100 gitea-act.git 0.2.10-alt3: build FAILED
2024-May-28 13:39:32 :: [x86_64] requesting cancellation of task processing
[i586] golang.org/x/crypto@v0.22.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[i586] golang.org/x/net@v0.24.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[i586] golang.org/x/sys@v0.19.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[i586] golang.org/x/crypto@v0.19.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[i586] golang.org/x/net@v0.21.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[i586] golang.org/x/sys@v0.18.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[i586] golang.org/x/term@v0.18.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[i586] To ignore the vendor directory, use -mod=readonly or -mod=mod.
[i586] To sync the vendor directory, run:
[i586] go mod vendor
2024-May-28 13:39:33 :: [i586] gitea-act.git 0.2.10-alt3: remote: build failed
2024-May-28 13:39:33 :: [i586] #100 gitea-act.git 0.2.10-alt3: build FAILED
[aarch64] golang.org/x/crypto@v0.22.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[aarch64] golang.org/x/net@v0.24.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[aarch64] golang.org/x/sys@v0.19.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[aarch64] golang.org/x/crypto@v0.19.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[aarch64] golang.org/x/net@v0.21.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[aarch64] golang.org/x/sys@v0.18.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[aarch64] golang.org/x/term@v0.18.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[aarch64] To ignore the vendor directory, use -mod=readonly or -mod=mod.
[aarch64] To sync the vendor directory, run:
[aarch64] go mod vendor
2024-May-28 13:39:49 :: [aarch64] gitea-act.git 0.2.10-alt3: remote: build failed
2024-May-28 13:39:49 :: [aarch64] #100 gitea-act.git 0.2.10-alt3: build FAILED
[ppc64le] golang.org/x/crypto@v0.22.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[ppc64le] golang.org/x/net@v0.24.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[ppc64le] golang.org/x/sys@v0.19.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
[ppc64le] golang.org/x/crypto@v0.19.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[ppc64le] golang.org/x/net@v0.21.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[ppc64le] golang.org/x/sys@v0.18.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[ppc64le] golang.org/x/term@v0.18.0: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
[ppc64le] To ignore the vendor directory, use -mod=readonly or -mod=mod.
[ppc64le] To sync the vendor directory, run:
[ppc64le] go mod vendor
2024-May-28 13:39:54 :: [ppc64le] gitea-act.git 0.2.10-alt3: remote: build failed
2024-May-28 13:39:54 :: [ppc64le] #100 gitea-act.git 0.2.10-alt3: build FAILED
2024-May-28 13:39:32 :: [x86_64] build FAILED
2024-May-28 13:39:33 :: [i586] build FAILED
2024-May-28 13:39:49 :: [aarch64] build FAILED
2024-May-28 13:39:54 :: [ppc64le] build FAILED
2024-May-28 13:39:55 :: task #349723 for sisyphus FAILED
next reply other threads:[~2024-05-28 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 13:39 Girar awaiter (shaba) [this message]
2024-05-28 14:03 ` [#349723] DONE (try 2) gitea-act.git=0.2.10-alt3 Girar pender (shaba)
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.349723.1.1@gyle.mskdc.altlinux.org \
--to=girar-builder@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=girar-builder-sisyphus@altlinux.org \
--cc=shaba@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