From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cryptsetup: update to 2.5.0.
Date: Tue, 18 Oct 2022 00:07:57 +0200 [thread overview]
Message-ID: <20221017220757.48GugqZ51iw3f0rejYwxufkgm1rwbmTDbt1lFgn2BOQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39446@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
New comment by motorto on void-packages repository
https://github.com/void-linux/void-packages/pull/39446#issuecomment-1281545775
Comment:
Yeah with CI I meant the chroot ...
Not sure if the failure is the same reason, let me check
Strike that, the tests that needs to be run as root locally are skipped at least on my x86_64-glibc.
=======================
All 9 tests passed
(22 tests were not run)
=======================
On 22/10/17 02:08PM, Piraty wrote:
> @Piraty commented on this pull request.
>
>
>
> > @@ -16,8 +16,8 @@ license="GPL-2.0-or-later"
> homepage="https://gitlab.com/cryptsetup/cryptsetup"
> changelog="https://gitlab.com/cryptsetup/cryptsetup/raw/master/docs/v${version}-ReleaseNotes"
> distfiles="${KERNEL_SITE}/utils/cryptsetup/v${version%.*}/${pkgname}-${version}.tar.xz"
> -checksum=fc0df945188172264ec5bf1d0bda08264fadc8a3f856d47eba91f31fe354b507
> -make_check=extended
> +checksum=9184a6ebbd9ce7eb211152e7f741a6c82f2d1cc0e24a84ec9c52939eee0f0542
> +make_check=ci-skip # tests depend on acessing /dev/mapper/control fails on CI
>
> some tests fail in local builds too
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/void-linux/void-packages/pull/39446#pullrequestreview-1144813989
> You are receiving this because you authored the thread.
>
> Message ID: ***@***.***>
next prev parent reply other threads:[~2022-10-17 22:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 14:10 [PR PATCH] " motorto
2022-09-25 9:47 ` [PR PATCH] [Updated] " motorto
2022-09-25 16:58 ` motorto
2022-09-25 19:14 ` motorto
2022-09-29 17:47 ` motorto
2022-09-29 18:06 ` motorto
2022-10-17 21:08 ` [PR REVIEW] " Piraty
2022-10-17 21:58 ` motorto
2022-10-17 22:07 ` motorto [this message]
2022-10-17 22:08 ` [PR REVIEW] " motorto
2022-10-17 22:09 ` motorto
2022-10-19 23:24 ` Piraty
2022-10-21 11:33 ` motorto
2022-10-23 11:47 ` [PR PATCH] [Updated] " motorto
2022-10-23 12:00 ` motorto
2022-10-27 17:49 ` motorto
2022-11-16 13:07 ` leahneukirchen
2022-11-16 18:59 ` [PR PATCH] [Updated] " motorto
2022-11-16 19:04 ` motorto
2022-11-16 20:57 ` [PR PATCH] [Merged]: " leahneukirchen
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=20221017220757.48GugqZ51iw3f0rejYwxufkgm1rwbmTDbt1lFgn2BOQ@z \
--to=motorto@users.noreply.github.com \
--cc=ml@inbox.vuxu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).