public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Viktor Malik <vmalik@redhat.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	song@kernel.org, yonghong.song@linux.dev,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
	haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
	shuah@kernel.org, memxor@gmail.com
Subject: Re: [PATCH bpf-next] selftests/bpf: skip the timer_lockup test for single-CPU nodes
Date: Sat, 09 Nov 2024 20:20:27 +0000	[thread overview]
Message-ID: <173118362751.3006527.5328856383741198318.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241107115231.75200-1-vmalik@redhat.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu,  7 Nov 2024 12:52:31 +0100 you wrote:
> The timer_lockup test needs 2 CPUs to work, on single-CPU nodes it fails
> to set thread affinity to CPU 1 since it doesn't exist:
> 
>     # ./test_progs -t test_lockup
>     test_timer_lockup:PASS:timer_lockup__open_and_load 0 nsec
>     test_timer_lockup:PASS:pthread_create thread1 0 nsec
>     test_timer_lockup:PASS:pthread_create thread2 0 nsec
>     timer_lockup_thread:PASS:cpu affinity 0 nsec
>     timer_lockup_thread:FAIL:cpu affinity unexpected error: 22 (errno 0)
>     test_timer_lockup:PASS: 0 nsec
>     #406     timer_lockup:FAIL
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: skip the timer_lockup test for single-CPU nodes
    https://git.kernel.org/bpf/bpf-next/c/5bfc4f22e0d7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-11-09 20:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 11:52 [PATCH bpf-next] selftests/bpf: skip the timer_lockup test for single-CPU nodes Viktor Malik
2024-11-08  4:41 ` Philo Lu
2024-11-09 20:06   ` Kumar Kartikeya Dwivedi
2024-11-09 20:20 ` patchwork-bot+netdevbpf [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=173118362751.3006527.5328856383741198318.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=mykolal@fb.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=vmalik@redhat.com \
    --cc=yonghong.song@linux.dev \
    /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