From: Gustavo Sousa <gustavo.sousa@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [PATCH i-g-t 0/3] Add support for hook script
Date: Thu, 9 May 2024 12:24:28 -0300 [thread overview]
Message-ID: <20240509152442.189166-1-gustavo.sousa@intel.com> (raw)
For development purposes, sometimes it is useful to have a way of
running custom scripts at certain points of test executions. A
real-world example I bumped into recently is to collect information from
sysfs before and after running each entry of a testlist.
While it is possible for the user to handcraft a script that calls each
test with the correct actions before and after execution, we can provide
a better experience by adding built-in support for running hooks during
test execution.
This series adds support for running a hook script during test
execution. The feature is exposed to users via option --hook, which made
available for regular test binaries as well as for igt_runner.
Gustavo Sousa (3):
igt_hook: Add feature
runner: Make it easier to extend argv
runner: Add option --hook
.../igt-gpu-tools/igt-gpu-tools-docs.xml | 1 +
lib/igt_core.c | 116 +++-
lib/igt_hook.c | 499 ++++++++++++++++++
lib/igt_hook.h | 86 +++
lib/meson.build | 1 +
lib/tests/igt_hook.c | 187 +++++++
lib/tests/igt_hook_integration.c | 297 +++++++++++
lib/tests/meson.build | 2 +
runner/executor.c | 52 +-
runner/runner_tests.c | 5 +
runner/settings.c | 25 +-
runner/settings.h | 1 +
12 files changed, 1248 insertions(+), 24 deletions(-)
create mode 100644 lib/igt_hook.c
create mode 100644 lib/igt_hook.h
create mode 100644 lib/tests/igt_hook.c
create mode 100644 lib/tests/igt_hook_integration.c
--
2.45.0
next reply other threads:[~2024-05-09 15:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 15:24 Gustavo Sousa [this message]
2024-05-09 15:24 ` [PATCH i-g-t 1/3] igt_hook: Add feature Gustavo Sousa
2024-05-13 17:10 ` Kamil Konieczny
2024-05-15 17:10 ` Kamil Konieczny
2024-05-15 17:35 ` Gustavo Sousa
2024-05-16 10:40 ` Kamil Konieczny
2024-05-16 12:19 ` Gustavo Sousa
2024-05-16 16:30 ` Kamil Konieczny
2024-05-16 17:05 ` Gustavo Sousa
2024-05-20 19:03 ` Lucas De Marchi
2024-05-21 19:40 ` Lucas De Marchi
2024-06-19 21:12 ` Gustavo Sousa
2024-05-09 15:24 ` [PATCH i-g-t 2/3] runner: Make it easier to extend argv Gustavo Sousa
2024-05-09 15:24 ` [PATCH i-g-t 3/3] runner: Add option --hook Gustavo Sousa
2024-05-09 16:13 ` ✗ GitLab.Pipeline: warning for Add support for hook script Patchwork
2024-05-09 17:04 ` Gustavo Sousa
2024-05-20 19:44 ` Lucas De Marchi
2024-06-19 19:07 ` Gustavo Sousa
2024-05-09 16:24 ` ✓ CI.xeBAT: success " Patchwork
2024-05-09 16:33 ` ✓ Fi.CI.BAT: " Patchwork
2024-05-09 21:12 ` ✗ CI.xeFULL: failure " Patchwork
2024-05-10 5:30 ` ✗ 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=20240509152442.189166-1-gustavo.sousa@intel.com \
--to=gustavo.sousa@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