From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/3] ./scripts/igt_doc.py: speedup check logic
Date: Wed, 12 Apr 2023 14:35:42 +0200 [thread overview]
Message-ID: <20230412123544.119534-1-mauro.chehab@linux.intel.com> (raw)
From: Mauro Carvalho Chehab <mchehab@kernel.org>
The logic which checks for missing/obsolete documentation is too
slow. Currently, on my notebook it takes 12 seconds:
$ time ./scripts/igt_doc.py --check --config tests/xe/xe_*json
real 0m12.085s
user 0m10.468s
sys 0m1.457s
Implent it on a different way, in order to speedup the build process.
After the change, it now takes less than 500ms:
$ time ./scripts/igt_doc.py --check --config tests/xe/xe_*json
real 0m0.460s
user 0m0.357s
sys 0m0.102s
Mauro Carvalho Chehab (3):
scripts/igt_doc.py: cleanup some pylint warnings
scripts/igt_doc.py: don't depend on igt_runner anymore
scripts/test_list.py: use a compiled regex for check
docs/testplan/meson.build | 7 ++--
scripts/igt_doc.py | 11 +++----
scripts/test_list.py | 69 +++++++++++++++++++++++++++------------
3 files changed, 54 insertions(+), 33 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-12 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 12:35 Mauro Carvalho Chehab [this message]
2023-04-12 12:35 ` [igt-dev] [PATCH i-g-t 1/3] scripts/igt_doc.py: cleanup some pylint warnings Mauro Carvalho Chehab
2023-04-12 12:35 ` [igt-dev] [PATCH i-g-t 2/3] scripts/igt_doc.py: don't depend on igt_runner anymore Mauro Carvalho Chehab
2023-04-12 12:35 ` [igt-dev] [PATCH i-g-t 3/3] scripts/test_list.py: use a compiled regex for check Mauro Carvalho Chehab
2023-04-12 13:24 ` [igt-dev] ✓ Fi.CI.BAT: success for ./scripts/igt_doc.py: speedup check logic Patchwork
2023-04-12 21:51 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20230412123544.119534-1-mauro.chehab@linux.intel.com \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.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