Linux Perf Users
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@arm.com>
To: Lalit Maganti <lalitmaganti@gmail.com>
Cc: irogers@google.com, alice.mei.rogers@gmail.com, acme@kernel.org,
	namhyung@kernel.org, james.clark@linaro.org, leo.yan@linux.dev,
	adrian.hunter@intel.com, linux-perf-users@vger.kernel.org
Subject: Re: perf build: default build fails in pylint (pylint 4, missing optional modules)
Date: Fri, 23 Oct 2026 14:40:45 +0100	[thread overview]
Message-ID: <20261023134045.GJ26205@e132581.arm.com> (raw)
In-Reply-To: <20261018070110.927636-1-lalitmaganti@gmail.com>

On Sun, Oct 18, 2026 at 08:01:10AM +0100, Lalit Maganti wrote:

[...]

> Since 5fe83fb352c8 ("perf build: Make pylint build test opt-out
> (NO_PYLINT=1)") the build runs pylint whenever it is installed, and a
> default build of perf-tools-next (1c90f0a3c8a1) now fails in pylint for
> me, on Fedora 44 with Python 3.14.8 and pylint 4.1.3. With make -k, four
> files fail:
> 
>   python/treport.py:625:8: W0201: Attribute 'sub_title' defined outside __init__ (attribute-defined-outside-init)
>   python/ttimechart.py:1086:8: W0201: Attribute 'virtual_size' defined outside __init__ (attribute-defined-outside-init)
>   (and a few more of the same kinds in treport.py and ttimechart.py)

I try to avoid duplicating others' work, but our CI failed to build perf
due to W0201 warning, so I sent two patches to fix it:
https://lore.kernel.org/linux-perf-users/20261023-perf_fix_pylint_warning-v1-0-b9da8dae2fe9@arm.com/T/#t

I haven't found other reported issues so far, so I'll leave it to Ian
and Alice to take a look.

Thanks,
Leo

      reply	other threads:[~2026-10-23 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18  7:01 perf build: default build fails in pylint (pylint 4, missing optional modules) Lalit Maganti
2026-10-23 13:40 ` Leo Yan [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=20261023134045.GJ26205@e132581.arm.com \
    --to=leo.yan@arm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alice.mei.rogers@gmail.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=lalitmaganti@gmail.com \
    --cc=leo.yan@linux.dev \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.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