From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Failure of func-x86_64-memlock
Date: Fri, 05 Sep 2025 13:11:15 +0100 [thread overview]
Message-ID: <87ldmtw13w.fsf@draig.linaro.org> (raw)
In-Reply-To: <7ceb8d59-be3f-4dad-9e2b-9db62fbf92cb@linaro.org> (Richard Henderson's message of "Fri, 5 Sep 2025 12:26:08 +0200")
Richard Henderson <richard.henderson@linaro.org> writes:
> Hi guys,
>
> This test has been failing on my laptop for a few weeks.
> Any idea why?
>
> There's nothing logged in tests/functional/x86_64/test_memlock*/*,
> which itself seems like a bug.
I wonder who actually is running the test because:
@skipLockedMemoryTest(2_097_152) # 2GB
means it just skips for me on my beefy desktop.
>
>
> r~
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-09-05 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 10:26 Failure of func-x86_64-memlock Richard Henderson
2025-09-05 12:11 ` Alex Bennée [this message]
2025-09-08 10:12 ` Thomas Huth
2025-09-09 7:48 ` Richard Henderson
2025-09-09 9:19 ` Thomas Huth
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=87ldmtw13w.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).