From: Chris Hofstaedtler <zeha@debian.org>
To: util-linux@vger.kernel.org
Cc: 1138789@bugs.debian.org,
"Johannes Wüller" <johanneswueller@gmail.com>,
debian-loongarch@lists.debian.org
Subject: Re: Bug#1138789: FTBFS on loong64: mkswap: error: swap area needs to be at least 160 KiB
Date: Wed, 3 Jun 2026 22:04:36 +0200 [thread overview]
Message-ID: <aiCI1IeBms90Uzy0@per.namespace.at> (raw)
In-Reply-To: <aiCHUJ8pmy_Atx2S@per.namespace.at>
Hi Johannes, Karel,
util-linux 2.42.1 apparently fails its mkswap tests on loong64. Given
it fails in mkswap/mkswap-file-existing, I suspect this is "caused"
by commit 775729884a3945a53df33e0d3ff2ba263b96b59e /
6d87ff51568c017a6d08043d554bf0ea8dee5457.
Could you take a look please?
> diff-{{{
> --- /dev/null 2026-05-29 12:41:25.961759630 +0000
> +++ /build/reproducible-path/util-linux-2.42.1/tests/output/mkswap/mkswap-file-existing 2026-06-03 19:26:30.186627085 +0000
> @@ -0,0 +1,3 @@
> +mkswap failed
> +mkswap: error: swap area needs to be at least 160 KiB
> +mkswap -F failed on existing file
> }}}-diff
>
> FAILED (mkswap/mkswap-file-existing)
> ========= script: /build/reproducible-path/util-linux-2.42.1/tests/ts/mkswap/mkswap =================
> ================= OUTPUT =====================
> 1 mkswap failed
> 2 mkswap: error: swap area needs to be at least 160 KiB
> 3 mkswap -F failed on existing file
>
Full build log at:
https://buildd.debian.org/status/fetch.php?pkg=util-linux&arch=loong64&ver=2.42.1-1&stamp=1780514831&file=log
Many thanks!
Chris
next parent reply other threads:[~2026-06-03 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aiCHUJ8pmy_Atx2S@per.namespace.at>
2026-06-03 20:04 ` Chris Hofstaedtler [this message]
2026-06-04 12:20 ` [PATCH] mkswap: use 64k pages in file-existing test Chris Hofstaedtler
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=aiCI1IeBms90Uzy0@per.namespace.at \
--to=zeha@debian.org \
--cc=1138789@bugs.debian.org \
--cc=debian-loongarch@lists.debian.org \
--cc=johanneswueller@gmail.com \
--cc=util-linux@vger.kernel.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