Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v4 0/6] Speedup IGT build time
Date: Mon, 10 Jul 2023 08:16:15 +0200	[thread overview]
Message-ID: <20230710061621.671843-1-mauro.chehab@linux.intel.com> (raw)

From: Mauro Carvalho Chehab <mchehab@kernel.org>

Currently, even a single change on IGT makes the build time too
slow.

This is because it will re-generate the check testlist on every
single build that touches any file.

Change the logic to generate per-file testlists, with speeds up
build time from 22 seconds to 4 seconds.

It can be improved even further after changing the build logic
to maintain separate test_executables for i915, kms and xe.

As there's a pending patch series touching those tests, moving
them to tests/intel directory, let's not do a conflicting change.
Once such patch series gets merged, I'll write a patch with the
pending optimization.

---

v4:
- fix dependency chain for igt-doc.py;
- create an intel-ci.testlist with core tests and tests for
  intel drivers.

v3:
- custom_target that generates testlist is now simpler and
  should work better.

v2:
- make it compatible with Meson 0.47;
- added a patch to simplify tests/meson.build
- dropped a change at gem_stress - maybe there's a real reason
  why this one was excluded from test_list, so let's keep it
  as-is.

Mauro Carvalho Chehab (6):
  tests/meson.build: Simplify builds for core and i915 targets
  lib/igt_core: use the macro when checking for list_subtests
  lib/igt_core: add an option to show the testlist
  tests/meson.build: create testlists for tests
  scripts/test_list.py: speedup testlist check logic
  tests/build: Generate and store an intel-ci.testlist

 docs/testplan/meson.build  |   2 +-
 lib/igt_core.c             |  26 +++-
 scripts/test_list.py       |  30 +---
 tests/intel-ci/meson.build |   8 ++
 tests/meson.build          | 272 +++++++++++++++----------------------
 5 files changed, 141 insertions(+), 197 deletions(-)

-- 
2.40.1

             reply	other threads:[~2023-07-10  6:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10  6:16 Mauro Carvalho Chehab [this message]
2023-07-10  6:16 ` [igt-dev] [PATCH i-g-t v4 1/6] tests/meson.build: Simplify builds for core and i915 targets Mauro Carvalho Chehab
2023-07-10  6:16 ` [igt-dev] [PATCH i-g-t v4 2/6] lib/igt_core: use the macro when checking for list_subtests Mauro Carvalho Chehab
2023-07-10  6:16 ` [igt-dev] [PATCH i-g-t v4 3/6] lib/igt_core: add an option to show the testlist Mauro Carvalho Chehab
2023-07-10  6:16 ` [igt-dev] [PATCH i-g-t v4 4/6] tests/meson.build: create testlists for tests Mauro Carvalho Chehab
2023-07-10  6:16 ` [igt-dev] [PATCH i-g-t v4 5/6] scripts/test_list.py: speedup testlist check logic Mauro Carvalho Chehab
2023-07-10  6:16 ` [igt-dev] [PATCH i-g-t v4 6/6] tests/build: Generate and store an intel-ci.testlist Mauro Carvalho Chehab
2023-07-10  7:21 ` [igt-dev] ✗ Fi.CI.BAT: failure for Speedup IGT build time (rev5) Patchwork
2023-07-10  7:30 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-07-10 10:12 ` 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=20230710061621.671843-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