public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: IGT development <igt-dev@lists.freedesktop.org>
Cc: Petri Latvala <petri.latvala@intel.com>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: [igt-dev] [PATCH i-g-t 3/5] tests: drop invalid name build checks
Date: Tue, 19 Feb 2019 08:57:14 +0100	[thread overview]
Message-ID: <20190219075716.11553-3-daniel.vetter@ffwll.ch> (raw)
In-Reply-To: <20190219075716.11553-1-daniel.vetter@ffwll.ch>

They're causing troubles because this runs all the igt_fixtures, and
doing that on a build machine is at best surprising.

The main aim for this is catching testcases which fail to call
igt_exit. But just enumerating subtests does that too, and we have
library unit tests to make sure that's the case (with igt_no_exit and
igt_no_exit_list_only).

Cc: Petri Latvala <petri.latvala@intel.com>
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
 tests/igt_command_line.sh | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/tests/igt_command_line.sh b/tests/igt_command_line.sh
index e05ec34ce321..92643c4d5e16 100755
--- a/tests/igt_command_line.sh
+++ b/tests/igt_command_line.sh
@@ -94,10 +94,6 @@ check_test ()
 			fail $test
 		fi
 	fi
-
-	# check invalid subtest handling
-	echo "  Checking invalid subtest handling..."
-	./$test --run-subtest invalid-subtest > /dev/null 2>&1 && fail $test
 }
 
 TESTLISTFILE="$tests_dir/test-list.txt"
-- 
2.20.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2019-02-19  7:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  7:57 [igt-dev] [PATCH i-g-t 1/5] lib/tests: Add header for common helpers Daniel Vetter
2019-02-19  7:57 ` [igt-dev] [PATCH i-g-t 2/5] lib/tests: add internal_assert_wexited/wsignaled Daniel Vetter
2019-02-19  8:52   ` Chris Wilson
2019-02-19  7:57 ` Daniel Vetter [this message]
2019-02-19  9:06   ` [igt-dev] [PATCH i-g-t 3/5] tests: drop invalid name build checks Arkadiusz Hiler
2019-02-19  7:57 ` [igt-dev] [PATCH i-g-t 4/5] lib/tests: Convert no_exit tests into positive tests Daniel Vetter
2019-02-20 11:10   ` Arkadiusz Hiler
2019-02-19  7:57 ` [igt-dev] [PATCH i-g-t 5/5] lib/tests: Add testcase for nonexisting subtest name Daniel Vetter
2019-02-20 11:22   ` Arkadiusz Hiler
2019-02-20 12:57     ` Daniel Vetter
2019-02-19  8:41 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] lib/tests: Add header for common helpers Patchwork
2019-02-19  9:48 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-20 11:09 ` [igt-dev] [PATCH i-g-t 1/5] " Arkadiusz Hiler

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=20190219075716.11553-3-daniel.vetter@ffwll.ch \
    --to=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@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