All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH i-g-t 1/3] igt_command_line.sh: Handle the special cases of drv_selftest and drm_mm
Date: Tue, 21 Mar 2017 14:50:08 +0200	[thread overview]
Message-ID: <1490100610-3069-1-git-send-email-petri.latvala@intel.com> (raw)

Kernel selftest launchers use dynamic subtest enumeration. When
running on a kernel without selftests, they output nothing from
--list-subtests and exit with 0. Handle this specialty in the checker.

Signed-off-by: Petri Latvala <petri.latvala@intel.com>
---
 tests/igt_command_line.sh | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/tests/igt_command_line.sh b/tests/igt_command_line.sh
index a20e44c..69fa843 100755
--- a/tests/igt_command_line.sh
+++ b/tests/igt_command_line.sh
@@ -81,7 +81,12 @@ for test in $TESTLIST; do
 	fi
 
 	if [ $RET -eq 0 -a -z "$LIST" ]; then
-		fail $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" != "drv_selftest" -a "$testname" != "drm_mm" ]; then
+			fail $test
+		fi
 	fi
 
 	# check invalid subtest handling
-- 
2.9.3

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2017-03-21 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 12:50 Petri Latvala [this message]
2017-03-21 12:50 ` [PATCH i-g-t 2/3] igt_command_line.sh: Actually check things during distcheck Petri Latvala
2017-03-21 12:50 ` [PATCH i-g-t 3/3] lib/igt_kmod: Don't call igt_assert or igt_require without a fixture Petri Latvala

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=1490100610-3069-1-git-send-email-petri.latvala@intel.com \
    --to=petri.latvala@intel.com \
    --cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.