From: Mark Brown <broonie@kernel•org>
To: Ankur Arora <ankur.a.arora@oracle•com>
Cc: Andrew Morton <akpm@linux-foundation•org>,
Mark Rutland <mark.rutland@arm•com>,
Will Deacon <will@kernel•org>,
Catalin Marinas <catalin.marinas@arm•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: test failure after merge of the mm-nonmm-unstable tree
Date: Tue, 19 May 2026 09:26:25 +0100 [thread overview]
Message-ID: <6c01ab97-e3d4-42ae-bdce-b73d660fe68d@sirena.org.uk> (raw)
In-Reply-To: <87mrxwndhl.fsf@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
On Mon, May 18, 2026 at 11:02:30PM -0700, Ankur Arora wrote:
> Ankur Arora <ankur.a.arora@oracle•com> writes:
> > Mark Brown <broonie@kernel•org> writes:
> >>> Note that we are running on an arm64 host with access to KVM so the
> >>> above should be running with KVM rather than being emulated.
> > Possibly because the we got scheduled out while running the test. Not
> > sure why the test started failing now. I'm guessing the VM running the
> > test isn't under CPU stress and the like.
Yes, the system should be doing nothing except run KUnit and any random
background stuff, it's pretty high end so any background stuff shouldn't
need to disturb KUnit. At some point I will go back to running multiple
tests in parallel but didn't do that yet.
As I indicated above I'm fairly sure the main difference is that I'm
running on actual hardware not emulation, though I do think there's
something else that made it more prominent in that situation. I'm
fairly sure Thierry was using emulation while he was running -next.
> > If that can happen then I should relax the second condition.
> Thinking some more, the condition is much too strict.
> Instead of:
> succeeds => (runtime <= timeout_ns)
> A better check would be:
> !succeeds => runtime >= timeout_ns
> I'll send a patch to that effect.
Hopefully that's it...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-05-19 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 12:00 linux-next: test failure after merge of the mm-nonmm-unstable tree Mark Brown
2026-05-18 13:49 ` Mark Brown
2026-05-18 19:15 ` Ankur Arora
2026-05-19 6:02 ` Ankur Arora
2026-05-19 8:26 ` Mark Brown [this message]
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=6c01ab97-e3d4-42ae-bdce-b73d660fe68d@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=ankur.a.arora@oracle$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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