From: Daniel Vetter <daniel@ffwll.ch>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] tests: ddx_intel_after_fbdev loads intel ddx after fbdev was loaded.
Date: Wed, 21 Aug 2013 14:03:31 +0200 [thread overview]
Message-ID: <20130821120331.GD26909@phenom.ffwll.local> (raw)
In-Reply-To: <CABVU7+sCe7w8-z_VFgS-ewi487FfO55w-wb4-t0PO3c1a_f3cA@mail.gmail.com>
On Wed, Aug 21, 2013 at 1:55 PM, Rodrigo Vivi <rodrigo.vivi@gmail.com> wrote:
> On Wed, Aug 21, 2013 at 6:27 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> On Wed, Aug 21, 2013 at 11:16 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>>> On Wed, Aug 21, 2013 at 11:00:53AM +0200, Daniel Vetter wrote:
>>>> On Tue, Aug 20, 2013 at 03:43:05PM -0300, Rodrigo Vivi wrote:
>>>> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
>>>>
>>>> I'm confused what exactly this tests, since it seems to never fail ...
>
> fb.o #68030
>
>>>> automated tests should have some checks for expected results.
>>>>
>>>> Also I'm not sure whether we want such ddx/X tests in igt ...
>
> actually it was your idea and I liked it ;)
Ah, what I meant was a reduced testcase to replay just the special
modesetting sequence to reproduce the bug. Similar to what Imre recently
has done with the kms_setmode.c testcase. If we add the entire script we
essentially depend upon fbdev and our own ddx to not change behaviour ...
>>> Whether or not it makes a good test, it is nice to have a repository of
>>> the little hacks we use for debugging. From little acorns mighty oaks
>>> grow.
>>
>> Agreed, but then it imo shouldn't be added to the default list of
>> targets of tests to run.
>
> Agreed. tbh I didn't realized I was doing that by adding it to TESTS_scripts
>
>> We already have a bunch of these scripts
>> added to EXTRA_DIST, I guess adding a new variable SCRIPTS would be
>> good.
>
> Do you think we need an extra directory for scripts like this? or just
> create this new SCRIPTS variable at Makefile.am?
Since it's essentially a special testcase script I think tests/ is good
enough. Something like the below diff:
Cheers, Daniel
diff --git a/tests/Makefile.am b/tests/Makefile.am
index ddb709f..805d90f 100644
--- a/tests/Makefile.am
+++ b/tests/Makefile.am
@@ -170,8 +170,14 @@ HANG = \
gem_non_secure_batch \
$(NULL)
+scripts = \
+ check_drm_clients \
+ debugfs_wedged\
+ drm_lib.sh \
+ $(NULL)
+
EXTRA_PROGRAMS = $(TESTS_progs) $(TESTS_progs_M) $(HANG)
-EXTRA_DIST = $(TESTS_scripts) $(TESTS_scripts_M) drm_lib.sh check_drm_clients debugfs_wedged
+EXTRA_DIST = $(TESTS_scripts) $(TESTS_scripts_M) $(scripts)
CLEANFILES = $(EXTRA_PROGRAMS)
AM_CFLAGS = $(DRM_CFLAGS) $(CWARNFLAGS) \
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-08-21 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 18:43 [PATCH] tests: ddx_intel_after_fbdev loads intel ddx after fbdev was loaded Rodrigo Vivi
2013-08-21 9:00 ` Daniel Vetter
2013-08-21 9:16 ` Chris Wilson
2013-08-21 9:27 ` Daniel Vetter
2013-08-21 11:55 ` Rodrigo Vivi
2013-08-21 12:03 ` Daniel Vetter [this message]
2013-08-21 12:26 ` Rodrigo Vivi
2013-08-21 18:13 ` Rodrigo Vivi
2013-08-21 21:18 ` Daniel Vetter
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=20130821120331.GD26909@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.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 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.