mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, allen.lkml@gmail.com,
	"Mickaël Salaün" <mic@digikod.net>
Subject: Re: [PATCH 6.9 000/197] 6.9.9-rc1 review
Date: Wed, 10 Jul 2024 18:20:49 +0100	[thread overview]
Message-ID: <Zo7C8W97URxXYXd-@finisterre.sirena.org.uk> (raw)
In-Reply-To: <Zo6G9C-AzU2jBrOt@finisterre.sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

On Wed, Jul 10, 2024 at 02:04:55PM +0100, Mark Brown wrote:

> # #  RUN           rtc.date_read_loop ...
> # # rtctest.c:95:date_read_loop:Continuously reading RTC time for 30s (with 11ms breaks after every read).
> # # rtctest.c:122:date_read_loop:Performed 2954 RTC time reads.
> # #            OK  rtc.date_read_loop

> Bisection points to "selftests/harness: Fix tests timeout and race
> condition" but this looks like a test bug, the timeout for tests is 30s
> and the test tries to run for 30s which obviously doesn't add up.
> Previously the test would pass because the bug the patch is fixing is
> that timeout had no effect.  I'm also running the test on other
> platforms without it triggering new timeouts, it's just this one
> specific platform that triggered which is a bit worrying.

> I'll send a patch for the test.

Sorry, spoke too soon on that - the test is explicitly overriding the
timeout to be longer so there's something else going on here.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-07-10 17:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 11:07 Greg Kroah-Hartman
2024-07-09 18:42 ` SeongJae Park
2024-07-09 18:58 ` Markus Reichelt
2024-07-09 19:49 ` Pavel Machek
2024-07-09 20:01 ` Kelsey Steele
2024-07-09 23:21 ` Shuah Khan
2024-07-09 23:24 ` Peter Schneider
2024-07-10  2:36 ` Bagas Sanjaya
2024-07-10  3:11 ` Naresh Kamboju
2024-07-11  8:30   ` Naresh Kamboju
2024-07-11  9:11     ` Greg Kroah-Hartman
2024-07-11 12:29       ` Naresh Kamboju
2024-07-10  8:34 ` Jon Hunter
2024-07-10  9:07 ` Christian Heusel
2024-07-10 11:01 ` Pascal Ernster
2024-07-10 12:59 ` Ron Economos
2024-07-10 13:04 ` Mark Brown
2024-07-10 17:20   ` Mark Brown [this message]
2024-07-12 17:38 ` Florian Fainelli
2024-07-09 15:18 Ronald Warsow

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=Zo7C8W97URxXYXd-@finisterre.sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mic@digikod.net \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®