From: vitaly prosyak <vprosyak@amd.com>
To: Peter Senna Tschudin <peter.senna@linux.intel.com>,
igt-dev@lists.freedesktop.org
Cc: vitaly.prosyak@amd.com, christian.koenig@amd.com,
alexander.deucher@amd.com, jesse.zhang@amd.com,
harry.wentland@amd.com, zbigniew.kempczynski@intel.com,
kamil.konieczny@linux.intel.com, ryszard.knop@intel.com,
lucas.demarchi@intel.com, katarzyna.piecielska@intel.com
Subject: Re: [PATCH v8 i-g-t 3/3] scripts/run-tests.sh: Add support to kmemleak and igt_facts
Date: Sun, 9 Mar 2025 23:07:43 -0400 [thread overview]
Message-ID: <0ed20d8c-532f-43f2-ac16-82866b641670@amd.com> (raw)
In-Reply-To: <20250307093426.90479-4-peter.senna@linux.intel.com>
Hi Peter,
Version 8 of your three patches looks good to me. However, I haven't tested them locally.
Let me know if you’d like us to run them locally ( not CI)
Thanks for the improvements!
Vitaly
On 2025-03-07 04:34, Peter Senna Tschudin wrote:
> 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.
>
> Cc: vitaly.prosyak@amd.com
> Cc: christian.koenig@amd.com
> Cc: alexander.deucher@amd.com
> Cc: jesse.zhang@amd.com
> Cc: harry.wentland@amd.com
> Cc: zbigniew.kempczynski@intel.com
> Cc: kamil.konieczny@linux.intel.com
> Cc: ryszard.knop@intel.com
> Cc: lucas.demarchi@intel.com
> Cc: katarzyna.piecielska@intel.com
> Reviewed-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
> 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
next prev parent reply other threads:[~2025-03-10 3:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 9:34 [PATCH v8 i-g-t 0/3] Integrate kmemleak scans in igt_runner Peter Senna Tschudin
2025-03-07 9:34 ` [PATCH v8 i-g-t 1/3] runner/kmemleak: library to interact with kmemleak Peter Senna Tschudin
2025-03-10 10:37 ` Kamil Konieczny
2025-03-07 9:34 ` [PATCH v8 i-g-t 2/3] runner/executor: Integrate igt_kmemleak scans Peter Senna Tschudin
2025-03-07 9:34 ` [PATCH v8 i-g-t 3/3] scripts/run-tests.sh: Add support to kmemleak and igt_facts Peter Senna Tschudin
2025-03-10 3:07 ` vitaly prosyak [this message]
2025-03-10 7:07 ` Peter Senna Tschudin
2025-03-10 20:05 ` vitaly prosyak
2025-03-12 22:35 ` vitaly prosyak
2025-03-17 8:43 ` Peter Senna Tschudin
2025-03-18 0:28 ` vitaly prosyak
2025-03-07 23:55 ` ✓ Xe.CI.BAT: success for Integrate kmemleak scans in igt_runner (rev6) Patchwork
2025-03-08 0:14 ` ✓ i915.CI.BAT: " Patchwork
2025-03-08 1:44 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-08 7:48 ` Peter Senna Tschudin
2025-03-10 16:17 ` Ravali, JupallyX
2025-03-09 10:52 ` ✗ Xe.CI.Full: " Patchwork
2025-03-10 7:01 ` Peter Senna Tschudin
2025-03-10 11:05 ` [PATCH v8 i-g-t 0/3] Integrate kmemleak scans in igt_runner Kamil Konieczny
2025-03-10 16:14 ` ✓ i915.CI.Full: success for Integrate kmemleak scans in igt_runner (rev6) 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=0ed20d8c-532f-43f2-ac16-82866b641670@amd.com \
--to=vprosyak@amd.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=harry.wentland@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jesse.zhang@amd.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=katarzyna.piecielska@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=peter.senna@linux.intel.com \
--cc=ryszard.knop@intel.com \
--cc=vitaly.prosyak@amd.com \
--cc=zbigniew.kempczynski@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