From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] [RFC] tests/meson.build: add gem_stress to test-list.txt
Date: Tue, 12 Sep 2023 12:30:11 +0200 [thread overview]
Message-ID: <20230912103011.88118-1-mauro.chehab@linux.intel.com> (raw)
From: Mauro Carvalho Chehab <mchehab@kernel.org>
Currently, gem_stress is a special case: while it is built,
igt_runner won't run it, as it doesn't belong to test-list.txt,
as it is not added to the list of executables, so the script
which generates test-list.txt silently ignores it.
Fix it by moving it to the list of tests that run on i915.
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
tests/meson.build | 14 +-------------
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/tests/meson.build b/tests/meson.build
index 92729e0c3c26..24b196037dd9 100644
--- a/tests/meson.build
+++ b/tests/meson.build
@@ -193,6 +193,7 @@ intel_i915_progs = [
'gem_shrink',
'gem_softpin',
'gem_spin_batch',
+ 'gem_stress',
'gem_streaming_writes',
'gem_sync',
'gem_tiled_blits',
@@ -485,19 +486,6 @@ foreach prog : test_list
test('testcase check ' + prog, test_script, args : prog)
endforeach
-testexe = executable('gem_stress', 'intel/gem_stress.c',
- install : true,
- install_dir : libexecdir,
- install_rpath : libexecdir_rpathdir,
- dependencies : igt_deps)
-if not meson.is_cross_build()
- testlist_files += custom_target('gem_stress.testlist',
- build_by_default : true,
- command : [testexe, '--show-testlist'],
- capture : true,
- output : 'gem_stress.testlist')
-endif
-
image_files = [
'1080p-left.png',
'1080p-right.png',
--
2.41.0
next reply other threads:[~2023-09-12 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 10:30 Mauro Carvalho Chehab [this message]
2023-09-12 14:05 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/meson.build: add gem_stress to test-list.txt Patchwork
2023-09-12 14:27 ` [igt-dev] ✓ CI.xeBAT: success " 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=20230912103011.88118-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