From: Tiffany Yang <ynaffit@google.com>
To: Carlos Llamas <cmllamas@google.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Christian Brauner" <brauner@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Kees Cook" <kees@kernel.org>,
kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] binder: mark binder_alloc_exhaustive_test as slow
Date: Fri, 24 Oct 2025 13:28:50 -0700 [thread overview]
Message-ID: <dbx8cy6cavst.fsf@ynaffit-alt.c.googlers.com> (raw)
In-Reply-To: <20251024161525.1732874-1-cmllamas@google.com> (Carlos Llamas's message of "Fri, 24 Oct 2025 16:15:02 +0000")
Carlos Llamas <cmllamas@google.com> writes:
> The binder_alloc_exhaustive_test kunit test takes over 30s to complete
> and the kunit framework reports:
> # binder_alloc_exhaustive_test: Test should be marked slow (runtime:
> 33.842881934s)
> Mark the test as suggested to silence the warning.
> Cc: Tiffany Yang <ynaffit@google.com>
> Signed-off-by: Carlos Llamas <cmllamas@google.com>
> ---
> drivers/android/tests/binder_alloc_kunit.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/drivers/android/tests/binder_alloc_kunit.c
> b/drivers/android/tests/binder_alloc_kunit.c
> index 9b884d977f76..7f9cc003bbe3 100644
> --- a/drivers/android/tests/binder_alloc_kunit.c
> +++ b/drivers/android/tests/binder_alloc_kunit.c
> @@ -554,7 +554,7 @@ static void binder_alloc_test_exit(struct kunit *test)
> static struct kunit_case binder_alloc_test_cases[] = {
> KUNIT_CASE(binder_alloc_test_init_freelist),
> KUNIT_CASE(binder_alloc_test_mmap),
> - KUNIT_CASE(binder_alloc_exhaustive_test),
> + KUNIT_CASE_SLOW(binder_alloc_exhaustive_test),
> {}
> };
Reviewed-by: Tiffany Yang <ynaffit@google.com>
--
Tiffany Y. Yang
next prev parent reply other threads:[~2025-10-24 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 16:15 Carlos Llamas
2025-10-24 20:28 ` Tiffany Yang [this message]
2025-10-27 11:40 ` Alice Ryhl
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=dbx8cy6cavst.fsf@ynaffit-alt.c.googlers.com \
--to=ynaffit@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=joelagnelf@nvidia.com \
--cc=kees@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=surenb@google.com \
--cc=tkjos@android.com \
/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®