From: Peter Senna Tschudin <peter.senna@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Peter Senna Tschudin <peter.senna@linux.intel.com>
Subject: [PATCH v7 i-g-t 3/3] scripts/run-tests.sh: Add support to kmemleak reports and igt_facts
Date: Thu, 27 Feb 2025 11:18:53 +0100 [thread overview]
Message-ID: <20250227101853.361504-4-peter.senna@linux.intel.com> (raw)
In-Reply-To: <20250227101853.361504-1-peter.senna@linux.intel.com>
Updates scripts/run-tests.sh to include the following options:
-f: enable igt_facts on igt_runner
-K <mode>: Linux Kernel kmemleak reports
- once: run a kmemleak scan after all tests
- each: run a kmemleak scan after each test
These options are simply relayed to igt_runner.
Signed-off-by: Peter Senna Tschudin <peter.senna@linux.intel.com>
---
scripts/run-tests.sh | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/scripts/run-tests.sh b/scripts/run-tests.sh
index 082ebaa5a..1fb9be478 100755
--- a/scripts/run-tests.sh
+++ b/scripts/run-tests.sh
@@ -132,9 +132,13 @@ print_help() {
echo " -P store code coverage results per each test. Should be"
echo " used together with -k option"
echo " -d download Piglit to $ROOT/piglit"
+ echo " -f enable igt_facts on igt_runner"
echo " -h display this help message"
echo " -k <kernel_dir> Linux Kernel source code directory used to generate code"
echo " coverage builds."
+ echo " -K <mode> Linux Kernel kmemleak reports"
+ echo " - once: run a kmemleak scan after all tests"
+ echo " - each: run a kmemleak scan after each test"
echo " -l list all available tests"
echo " -r <directory> store the results in directory"
echo " (default: $RESULTS)"
@@ -160,12 +164,14 @@ print_help() {
echo "Useful patterns for test filtering are described in the API documentation."
}
-while getopts ":c:dhk:lPr:st:T:vx:Rnpb:m:" opt; do
+while getopts ":c:dfhk:K:lPr:st:T:vx:Rnpb:m:" opt; do
case $opt in
c) COV_ARGS="$COV_ARGS --collect-code-cov --collect-script $OPTARG " ;;
d) download_piglit; exit ;;
+ f) IGT_FACTS="-f" ;;
h) print_help; exit ;;
k) IGT_KERNEL_TREE="$OPTARG" ;;
+ K) KMEMLEAK="--kmemleak=$OPTARG" ;;
l) LIST_TESTS="true" ;;
P) COV_ARGS="$COV_ARGS --coverage-per-test"; COV_PER_TEST=1 ;;
r) RESULTS="$OPTARG" ;;
@@ -256,7 +262,7 @@ if [ "x$RESUME_RUN" != "x" ]; then
execute_runner 1 $RESUME $RESUME_ARGS $COV_ARGS "$RESULTS"
else
mkdir -p "$RESULTS"
- execute_runner 1 $RUNNER $RUN_ARGS -o -s "$RESULTS" $COV_ARGS $VERBOSE $FILTER --prune-mode $PRUNE_MODE
+ execute_runner 1 $RUNNER $RUN_ARGS -o $IGT_FACTS $KMEMLEAK -s "$RESULTS" $COV_ARGS $VERBOSE $FILTER --prune-mode $PRUNE_MODE
fi
if [ "$SUMMARY" = "html" ]; then
--
2.34.1
next prev parent reply other threads:[~2025-02-27 10:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 10:18 [PATCH v7 i-g-t 0/3] Integrate kmemleak scans in igt_runner Peter Senna Tschudin
2025-02-27 10:18 ` [PATCH v7 i-g-t 1/3] runner/kmemleak: library to interact with kmemleak Peter Senna Tschudin
2025-02-28 7:04 ` Peter Senna Tschudin
2025-03-06 12:32 ` Kamil Konieczny
2025-03-07 3:59 ` vitaly prosyak
2025-03-06 12:02 ` Kamil Konieczny
2025-02-27 10:18 ` [PATCH v7 i-g-t 2/3] runner/executor: Integrate igt_kmemleak scans Peter Senna Tschudin
2025-02-28 7:05 ` Peter Senna Tschudin
2025-03-06 12:25 ` Kamil Konieczny
2025-02-27 10:18 ` Peter Senna Tschudin [this message]
2025-02-28 7:07 ` [PATCH v7 i-g-t 3/3] scripts/run-tests.sh: Add support to kmemleak reports and igt_facts Peter Senna Tschudin
2025-02-28 3:56 ` ✓ Xe.CI.BAT: success for Integrate kmemleak scans in igt_runner (rev5) Patchwork
2025-02-28 4:28 ` ✓ i915.CI.BAT: " Patchwork
2025-02-28 8:37 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-28 9:06 ` Peter Senna Tschudin
2025-02-28 11:53 ` Ravali, JupallyX
2025-03-05 7:28 ` ✗ i915.CI.Full: " Patchwork
2025-03-05 7:44 ` Peter Senna Tschudin
2025-03-05 16:12 ` Illipilli, TejasreeX
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=20250227101853.361504-4-peter.senna@linux.intel.com \
--to=peter.senna@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