From: Antonio Argenziano <antonio.argenziano@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] tests/igt_command_line.sh: Add new selftest for special handling
Date: Mon, 19 Aug 2019 15:31:37 -0700 [thread overview]
Message-ID: <20190819223137.3605-1-antonio.argenziano@intel.com> (raw)
dmabuf_selftests has been recently added to the test list but not added
to the special handling in igt_command_line.sh and therefore build
testing would fail.
Signed-off-by: Antonio Argenziano <antonio.argenziano@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
---
tests/igt_command_line.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/igt_command_line.sh b/tests/igt_command_line.sh
index 92643c4d..eaec1b4f 100755
--- a/tests/igt_command_line.sh
+++ b/tests/igt_command_line.sh
@@ -90,7 +90,7 @@ check_test ()
# Subtest enumeration of kernel selftest launchers depends
# on the running kernel. If selftests are not enabled,
# they will output nothing and exit with 0.
- if [ "$testname" != "i915_selftest" -a "$testname" != "drm_mm" -a "$testname" != "kms_selftest" ]; then
+ if [ "$testname" != "i915_selftest" -a "$testname" != "drm_mm" -a "$testname" != "kms_selftest" -a "$testname" != "dmabuf_selftests"]; then
fail $test
fi
fi
--
2.21.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-08-19 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 22:31 Antonio Argenziano [this message]
2019-08-19 23:37 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/igt_command_line.sh: Add new selftest for special handling Patchwork
2019-08-20 8:32 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2019-08-20 9:18 ` Petri Latvala
2019-08-20 8:51 ` Chris Wilson
2019-08-20 15:04 ` Antonio Argenziano
2019-08-23 9:25 ` Petri Latvala
2019-08-20 9:16 ` Petri Latvala
2019-08-20 11:36 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=20190819223137.3605-1-antonio.argenziano@intel.com \
--to=antonio.argenziano@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