From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
Jiri Olsa <jolsa@kernel.org>,
Clark Williams <williams@redhat.com>,
Kate Carcia <kcarcia@redhat.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Matthias Schwarzott <zzam@gentoo.org>,
Andrii Nakryiko <andrii@kernel.org>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
dwarves@vger.kernel.org
Subject: Re: [PATCH 2/5] tests default_vmlinux_btf: Introduce test for using BTF by default
Date: Tue, 19 Nov 2024 16:55:59 -0300 [thread overview]
Message-ID: <ZzztT0PIZ6sYEIbY@x1> (raw)
In-Reply-To: <020ec6550eb5e73bb5a273c57a686565a0a274df.camel@gmail.com>
On Tue, Nov 19, 2024 at 11:54:12AM -0800, Eduard Zingerman wrote:
> On Tue, 2024-11-19 at 16:49 -0300, Arnaldo Carvalho de Melo wrote:
> [...]
> > > Lgtm.
> > > Would it make sense to move this patch to the end of the series?
> > > In case someone does a bisect and runs the tests to find some regression.
>
> > Humm?
> > So you think it should be introduced only when it passes? I.e. when the
> > problem is fixed?
> Right.
> > My practice so far has been to reproduce the problem manually, write a
> > test, show that it detects the problem, fix, then show that the
> > regression test shows that the problem is not present anymore.
> Yes, the downside would be that anyone trying out the fix would
> need to do some rebase to try the test w/o fix.
> > I see your point about a bisection when running in the cset that
> > introduces the test case and in all before the fix is added will fail,
> > confusing the bisector or not allowing it to be automated :-\
> > So, yeah, probably, for automated bisection we should move it to after
> > the fix, when finishing the devel cycle, which is now, will do.
> Fwiw, that's what folks enforce for bpf selftests ¯\_(ツ)_/¯.
Makes sense, automated bisection trumps old practices :-)
- Arnaldo
next prev parent reply other threads:[~2024-11-19 19:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 20:41 [PATCH 0/5] Fix segfaults related to missing BTF support Arnaldo Carvalho de Melo
[not found] ` <20241118204146.772762-5-acme@kernel.org>
[not found] ` <20f6d8af-5c4e-4eb4-925e-7a6b10efcb55@oracle.com>
2024-11-19 17:46 ` [PATCH 4/5] tests default_vmlinux_btf: Cover the no args segfault too Arnaldo Carvalho de Melo
2024-11-19 17:51 ` Arnaldo Carvalho de Melo
[not found] ` <20241118204146.772762-6-acme@kernel.org>
[not found] ` <4b465bfc-8214-41ab-8b6d-bbdf7421e19b@oracle.com>
2024-11-19 18:29 ` [PATCH 5/5] core, libctf: Check if constructor arguments are NULL before using them Arnaldo Carvalho de Melo
[not found] ` <20241118204146.772762-2-acme@kernel.org>
[not found] ` <ac93d9fe-2e84-4e00-94ef-50a3074d49fc@oracle.com>
[not found] ` <ZzyO9aibti18J6sK@x1>
2024-11-19 17:48 ` [PATCH 1/5] core: Add method to get the vmlinux BTF filename, allow overriding it via env var Arnaldo Carvalho de Melo
[not found] ` <9992d2487775011278aef17d1a2db98b8cc74e7d.camel@gmail.com>
2024-11-19 18:32 ` Arnaldo Carvalho de Melo
[not found] ` <20241118204146.772762-3-acme@kernel.org>
[not found] ` <90d7282a-60af-4087-8e08-fed3fbe348ee@oracle.com>
2024-11-19 17:50 ` [PATCH 2/5] tests default_vmlinux_btf: Introduce test for using BTF by default Arnaldo Carvalho de Melo
[not found] ` <33b85d2c1adafb5a46a874dfcfd43682395e1564.camel@gmail.com>
2024-11-19 19:49 ` Arnaldo Carvalho de Melo
2024-11-19 19:54 ` Eduard Zingerman
2024-11-19 19:55 ` Arnaldo Carvalho de Melo [this message]
2024-11-19 20:12 ` Arnaldo Carvalho de Melo
2024-11-19 20:13 ` Eduard Zingerman
2024-11-19 20:15 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2024-11-19 13:40 [PATCH 0/5] Fix segfaults related to missing BTF support Arnaldo Carvalho de Melo
2024-11-19 13:40 ` [PATCH 2/5] tests default_vmlinux_btf: Introduce test for using BTF by default Arnaldo Carvalho de Melo
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=ZzztT0PIZ6sYEIbY@x1 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=jolsa@kernel.org \
--cc=kcarcia@redhat.com \
--cc=song@kernel.org \
--cc=williams@redhat.com \
--cc=yonghong.song@linux.dev \
--cc=zzam@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.