From: Namhyung Kim <namhyung@gmail.com>
To: Michael Petlan <mpetlan@redhat.com>
Cc: linux-perf-users@vger.kernel.org, acme@kernel.org,
acme@redhat.com, qzhao@redhat.com
Subject: Re: [PATCH 2/2] perf test: Fix JSON format linter test checks
Date: Tue, 24 Jan 2023 09:26:12 -0800 [thread overview]
Message-ID: <CAM9d7cip0KM-LJ_xdxvcL71E9BU31=PLZaJM-q7LawLQAScOqw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.20.2301241747420.5281@Diego>
On Tue, Jan 24, 2023 at 8:49 AM Michael Petlan <mpetlan@redhat.com> wrote:
>
> On Sun, 22 Jan 2023, Namhyung Kim wrote:
> > On Fri, Jan 20, 2023 at 6:00 AM Michael Petlan <mpetlan@redhat.com> wrote:
> > >
> > > The test fails on CPUs with topdown metrics, where it is common to print
> > > two metrics per line. Since these are included in default event set for
> > > `perf stat -- something`, it causes the "no args" subtest to fail due to
> > > unexpected member count. We need to accept 7 or 9 members in that case.
> > >
> > > Coming to that, counting commas in the JSON line and consider it a number
> > > of elements is incorrect and misleading. There should be +1 element than
> > > the count of commas, while also, commas can potentially appear in the
> > > event names. Count " : " substrings rather, since these better fit to
> > > what should be actually counted.
> >
> > I'm also curious if ":" could appear in the event/metric names.
> > Probably more chances to have ":" than "," in the name, no?
>
> Yes, ':' can appear in the event names, but not " : " (with the spaces
> around).
Ah, ok. Missed the whitespaces. :)
Thanks,
Namhyung
next prev parent reply other threads:[~2023-01-24 17:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 13:40 [PATCH 0/2] perf test: Fix JSON linter Michael Petlan
2023-01-20 13:40 ` [PATCH 1/2] perf stat: Fix JSON metric printout for multiple metrics per line Michael Petlan
2023-01-23 6:31 ` Namhyung Kim
2023-05-22 12:11 ` Michael Petlan
2023-06-06 11:16 ` Michael Petlan
2023-01-20 13:40 ` [PATCH 2/2] perf test: Fix JSON format linter test checks Michael Petlan
2023-01-23 6:36 ` Namhyung Kim
2023-01-24 16:49 ` Michael Petlan
2023-01-24 17:26 ` Namhyung Kim [this message]
2023-01-27 12:26 ` Arnaldo Carvalho de Melo
2023-01-27 12:30 ` Arnaldo Carvalho de Melo
2023-01-31 17:14 ` Michael Petlan
2023-02-02 1:18 ` Arnaldo Carvalho de Melo
2023-01-20 17:37 ` [PATCH 0/2] perf test: Fix JSON linter Ian Rogers
2023-01-23 6:48 ` Namhyung Kim
2023-01-23 13:38 ` Arnaldo Carvalho de Melo
2023-01-24 17:39 ` Michael Petlan
2023-01-25 0:37 ` Ian Rogers
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='CAM9d7cip0KM-LJ_xdxvcL71E9BU31=PLZaJM-q7LawLQAScOqw@mail.gmail.com' \
--to=namhyung@gmail.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.com \
--cc=qzhao@redhat.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;
as well as URLs for NNTP newsgroup(s).