From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] meson: Disable testplan build by default
Date: Wed, 12 Apr 2023 14:54:26 +0200 [thread overview]
Message-ID: <20230412145426.0c78ae49@maurocar-mobl2> (raw)
In-Reply-To: <ZDZe03xeOHW1VdcA@intel.com>
On Wed, 12 Apr 2023 10:33:39 +0300
Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Wed, Apr 12, 2023 at 09:26:29AM +0200, Mauro Carvalho Chehab wrote:
> > On Tue, 11 Apr 2023 14:02:05 +0300
> > Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> >
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > > No real idea what this "testplan" is and why it lives
> > > in igt. Seems to be build some xe documentation, and based
> > > on the name is maybe some manager level stuff? Surely
> > > this is nothing that matters for normal people (esp. those
> > > outside Intel).
> >
> > No. Basically, testplan contains documentation for the tests.
> > Currently, it contains 100% of the documentation from Xe tests.
> > We may end implementing it for i915 as well.
> >
> > There is even a plan to generate testlists like xe-fast-feedback.testlist
> > directly from documentation. So, it is important to have the tests properly
> > documented, as otherwise they won't be executed by CI in the future.
> >
> > >
> > > The main problem here being that it is hideously slow to
> > > build, making life miserable for everyone. Flip the
> > > default to disabled and let those that need this enable
> > > it themselves.
> >
> > Generating documents takes ~150ms. What makes it slow is not the doc
> > generation itself, but a validation logic that checks if the test
> > documentation was updated as tests got added/renamed/removed.
> > It currently uses igt_runner, pointing to the documented tests.
> > As right now just Xe tests uses it, it will call the runner with:
> >
> > $ igt_runner -L -t igt@xe ${builddir}/tests
>
> That is not the slow thing. The slow thing is some python stuff.
This was part of the slow logic. The other part is to run regular
expressions to check test names. This also needed some optimization.
Just sent a patch series using re.compile() to speed regexes, with
a replacement patch for igt_runner.
It could be possible to optimize it even further with multithreading
but as it is now taking 500ms to run (against 12 seconds before that on
a i7 notebook using python 3.11), it seems good enough to me after the
changes.
Patch series sent: https://patchwork.freedesktop.org/series/116379/
Regards,
Mauro
next prev parent reply other threads:[~2023-04-12 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 11:02 [igt-dev] [PATCH i-g-t] meson: Disable testplan build by default Ville Syrjala
2023-04-11 12:51 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-04-11 17:30 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-04-12 7:26 ` [igt-dev] [PATCH i-g-t] " Mauro Carvalho Chehab
2023-04-12 7:33 ` Ville Syrjälä
2023-04-12 12:54 ` Mauro Carvalho Chehab [this message]
2023-04-12 14:18 ` Ville Syrjälä
2023-04-13 9:19 ` Mauro Carvalho Chehab
2023-04-13 10:06 ` [igt-dev] ✗ Fi.CI.BAT: failure for meson: Disable testplan build by default (rev2) 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=20230412145426.0c78ae49@maurocar-mobl2 \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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