diff mbox

[RFC,i-g-t,3/3] tests: Add vc4 test suite

Message ID 20180305142129.18352-4-maxime.ripard@bootlin.com (mailing list archive)
State New, archived
Headers show

Commit Message

Maxime Ripard March 5, 2018, 2:21 p.m. UTC 
Add some various test suites relevant for the vc4 drm driver.

Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
---
 tests/vc4_ci/vc4-chamelium-fast.testlist |  4 ++++
 tests/vc4_ci/vc4-chamelium.testlist      |  9 ++++++++
 tests/vc4_ci/vc4.testlist                | 35 ++++++++++++++++++++++++++++++++
 3 files changed, 48 insertions(+)
 create mode 100644 tests/vc4_ci/vc4-chamelium-fast.testlist
 create mode 100644 tests/vc4_ci/vc4-chamelium.testlist
 create mode 100644 tests/vc4_ci/vc4.testlist

Comments

Petri Latvala March 13, 2018, 10:42 a.m. UTC | #1 
On Mon, Mar 05, 2018 at 03:21:29PM +0100, Maxime Ripard wrote:
> Add some various test suites relevant for the vc4 drm driver.
> 
> Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
> ---
>  tests/vc4_ci/vc4-chamelium-fast.testlist |  4 ++++
>  tests/vc4_ci/vc4-chamelium.testlist      |  9 ++++++++
>  tests/vc4_ci/vc4.testlist                | 35 ++++++++++++++++++++++++++++++++
>  3 files changed, 48 insertions(+)
>  create mode 100644 tests/vc4_ci/vc4-chamelium-fast.testlist
>  create mode 100644 tests/vc4_ci/vc4-chamelium.testlist
>  create mode 100644 tests/vc4_ci/vc4.testlist


Can you also add a README explaining where vc4_ci results can be found
(or statement for the lack of a public view) and how these testlist
files are used?

No general kms tests in vc4.testlist?

What is the contact information for people who will be responsible for
tests/vc4_ci?

FWIW,
Acked-by: Petri Latvala <petri.latvala@intel.com>




> 
> diff --git a/tests/vc4_ci/vc4-chamelium-fast.testlist b/tests/vc4_ci/vc4-chamelium-fast.testlist
> new file mode 100644
> index 000000000000..964167b82d00
> --- /dev/null
> +++ b/tests/vc4_ci/vc4-chamelium-fast.testlist
> @@ -0,0 +1,4 @@
> +igt@kms_chamelium@hdmi-crc-fast
> +igt@kms_chamelium@hdmi-edid-read
> +igt@kms_chamelium@hdmi-hpd
> +igt@kms_chamelium@hdmi-hpd-fast
> diff --git a/tests/vc4_ci/vc4-chamelium.testlist b/tests/vc4_ci/vc4-chamelium.testlist
> new file mode 100644
> index 000000000000..2651d03b6ceb
> --- /dev/null
> +++ b/tests/vc4_ci/vc4-chamelium.testlist
> @@ -0,0 +1,9 @@
> +igt@kms_chamelium@hdmi-crc-single
> +igt@kms_chamelium@hdmi-crc-multiple
> +igt@kms_chamelium@hdmi-frame-dump
> +igt@kms_chamelium@hdmi-hpd-storm
> +igt@kms_chamelium@hdmi-hpd-storm-disable
> +igt@kms_chamelium@hdmi-crc-fast
> +igt@kms_chamelium@hdmi-edid-read
> +igt@kms_chamelium@hdmi-hpd
> +igt@kms_chamelium@hdmi-hpd-fast
> diff --git a/tests/vc4_ci/vc4.testlist b/tests/vc4_ci/vc4.testlist
> new file mode 100644
> index 000000000000..e86d4c815c56
> --- /dev/null
> +++ b/tests/vc4_ci/vc4.testlist
> @@ -0,0 +1,35 @@
> +igt@vc4_create_bo@create-bo-0
> +igt@vc4_create_bo@create-bo-4096
> +igt@vc4_create_bo@create-bo-zeroed
> +igt@vc4_dmabuf_poll@poll-read-waits-until-write-done
> +igt@vc4_dmabuf_poll@poll-write-waits-until-write-done
> +igt@vc4_label_bo@set-label
> +igt@vc4_label_bo@set-bad-handle
> +igt@vc4_label_bo@set-bad-name
> +igt@vc4_label_bo@set-kernel-name
> +igt@vc4_lookup_fail@bad-color-write
> +igt@vc4_purgeable_bo@mark-willneed
> +igt@vc4_purgeable_bo@mark-purgeable
> +igt@vc4_purgeable_bo@mark-purgeable-twice
> +igt@vc4_purgeable_bo@access-purgeable-bo-mem
> +igt@vc4_purgeable_bo@access-purged-bo-mem
> +igt@vc4_purgeable_bo@mark-unpurgeable-check-retained
> +igt@vc4_purgeable_bo@mark-unpurgeable-purged
> +igt@vc4_purgeable_bo@free-purged-bo
> +igt@vc4_tiling@get-bad-handle
> +igt@vc4_tiling@set-bad-handle
> +igt@vc4_tiling@get-bad-flags
> +igt@vc4_tiling@set-bad-flags
> +igt@vc4_tiling@get-bad-modifier
> +igt@vc4_tiling@set-bad-modifier
> +igt@vc4_tiling@set-get
> +igt@vc4_tiling@get-after-free
> +igt@vc4_wait_bo@bad-bo
> +igt@vc4_wait_bo@bad-pad
> +igt@vc4_wait_bo@unused-bo-0ns
> +igt@vc4_wait_bo@unused-bo-1ns
> +igt@vc4_wait_bo@used-bo
> +igt@vc4_wait_bo@used-bo-0ns
> +igt@vc4_wait_bo@used-bo-1ns
> +igt@vc4_wait_seqno@bad-seqno-0ns
> +igt@vc4_wait_seqno@bad-seqno-1ns
> -- 
> 2.14.3
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Maxime Ripard March 13, 2018, 3:18 p.m. UTC | #2 
Hi,

On Tue, Mar 13, 2018 at 12:42:02PM +0200, Petri Latvala wrote:
> On Mon, Mar 05, 2018 at 03:21:29PM +0100, Maxime Ripard wrote:
> > Add some various test suites relevant for the vc4 drm driver.
> > 
> > Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
> > ---
> >  tests/vc4_ci/vc4-chamelium-fast.testlist |  4 ++++
> >  tests/vc4_ci/vc4-chamelium.testlist      |  9 ++++++++
> >  tests/vc4_ci/vc4.testlist                | 35 ++++++++++++++++++++++++++++++++
> >  3 files changed, 48 insertions(+)
> >  create mode 100644 tests/vc4_ci/vc4-chamelium-fast.testlist
> >  create mode 100644 tests/vc4_ci/vc4-chamelium.testlist
> >  create mode 100644 tests/vc4_ci/vc4.testlist
> 
> Can you also add a README explaining where vc4_ci results can be found
> (or statement for the lack of a public view) and how these testlist
> files are used?

There isn't any publicly visible CI plan at the moment (that I know
of). This patch was more to get a list of meaningful tests into the
tree so that the various people involved could share the tests run for
now at least. I'm not sure what the policy is for that to be honest.

> No general kms tests in vc4.testlist?
> 
> What is the contact information for people who will be responsible for
> tests/vc4_ci?

Eric? I guess that would be you?

Maxime
Petri Latvala March 14, 2018, 10:44 a.m. UTC | #3 
On Tue, Mar 13, 2018 at 04:18:54PM +0100, Maxime Ripard wrote:
> Hi,
> 
> On Tue, Mar 13, 2018 at 12:42:02PM +0200, Petri Latvala wrote:
> > On Mon, Mar 05, 2018 at 03:21:29PM +0100, Maxime Ripard wrote:
> > > Add some various test suites relevant for the vc4 drm driver.
> > > 
> > > Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
> > > ---
> > >  tests/vc4_ci/vc4-chamelium-fast.testlist |  4 ++++
> > >  tests/vc4_ci/vc4-chamelium.testlist      |  9 ++++++++
> > >  tests/vc4_ci/vc4.testlist                | 35 ++++++++++++++++++++++++++++++++
> > >  3 files changed, 48 insertions(+)
> > >  create mode 100644 tests/vc4_ci/vc4-chamelium-fast.testlist
> > >  create mode 100644 tests/vc4_ci/vc4-chamelium.testlist
> > >  create mode 100644 tests/vc4_ci/vc4.testlist
> > 
> > Can you also add a README explaining where vc4_ci results can be found
> > (or statement for the lack of a public view) and how these testlist
> > files are used?
> 
> There isn't any publicly visible CI plan at the moment (that I know
> of). This patch was more to get a list of meaningful tests into the
> tree so that the various people involved could share the tests run for
> now at least. I'm not sure what the policy is for that to be honest.


From IGT's side the policy is that the people who need such a
directory will set it up and it becomes their turf, in both
directions. Their responsibility to maintain, and their ack is
required for changes.
Maxime Ripard March 21, 2018, 10:41 a.m. UTC | #4 
Hi,

On Wed, Mar 14, 2018 at 12:44:10PM +0200, Petri Latvala wrote:
> On Tue, Mar 13, 2018 at 04:18:54PM +0100, Maxime Ripard wrote:
> > Hi,
> > 
> > On Tue, Mar 13, 2018 at 12:42:02PM +0200, Petri Latvala wrote:
> > > On Mon, Mar 05, 2018 at 03:21:29PM +0100, Maxime Ripard wrote:
> > > > Add some various test suites relevant for the vc4 drm driver.
> > > > 
> > > > Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
> > > > ---
> > > >  tests/vc4_ci/vc4-chamelium-fast.testlist |  4 ++++
> > > >  tests/vc4_ci/vc4-chamelium.testlist      |  9 ++++++++
> > > >  tests/vc4_ci/vc4.testlist                | 35 ++++++++++++++++++++++++++++++++
> > > >  3 files changed, 48 insertions(+)
> > > >  create mode 100644 tests/vc4_ci/vc4-chamelium-fast.testlist
> > > >  create mode 100644 tests/vc4_ci/vc4-chamelium.testlist
> > > >  create mode 100644 tests/vc4_ci/vc4.testlist
> > > 
> > > Can you also add a README explaining where vc4_ci results can be found
> > > (or statement for the lack of a public view) and how these testlist
> > > files are used?
> > 
> > There isn't any publicly visible CI plan at the moment (that I know
> > of). This patch was more to get a list of meaningful tests into the
> > tree so that the various people involved could share the tests run for
> > now at least. I'm not sure what the policy is for that to be honest.
> 
> From IGT's side the policy is that the people who need such a
> directory will set it up and it becomes their turf, in both
> directions. Their responsibility to maintain, and their ack is
> required for changes.

Ok, so I guess it would become mostly Eric's garden then :)

Eric, are you ok with such a test suite?

Maxime
diff mbox

Patch

diff --git a/tests/vc4_ci/vc4-chamelium-fast.testlist b/tests/vc4_ci/vc4-chamelium-fast.testlist
new file mode 100644
index 000000000000..964167b82d00
--- /dev/null
+++ b/tests/vc4_ci/vc4-chamelium-fast.testlist
@@ -0,0 +1,4 @@ 
+igt@kms_chamelium@hdmi-crc-fast
+igt@kms_chamelium@hdmi-edid-read
+igt@kms_chamelium@hdmi-hpd
+igt@kms_chamelium@hdmi-hpd-fast
diff --git a/tests/vc4_ci/vc4-chamelium.testlist b/tests/vc4_ci/vc4-chamelium.testlist
new file mode 100644
index 000000000000..2651d03b6ceb
--- /dev/null
+++ b/tests/vc4_ci/vc4-chamelium.testlist
@@ -0,0 +1,9 @@ 
+igt@kms_chamelium@hdmi-crc-single
+igt@kms_chamelium@hdmi-crc-multiple
+igt@kms_chamelium@hdmi-frame-dump
+igt@kms_chamelium@hdmi-hpd-storm
+igt@kms_chamelium@hdmi-hpd-storm-disable
+igt@kms_chamelium@hdmi-crc-fast
+igt@kms_chamelium@hdmi-edid-read
+igt@kms_chamelium@hdmi-hpd
+igt@kms_chamelium@hdmi-hpd-fast
diff --git a/tests/vc4_ci/vc4.testlist b/tests/vc4_ci/vc4.testlist
new file mode 100644
index 000000000000..e86d4c815c56
--- /dev/null
+++ b/tests/vc4_ci/vc4.testlist
@@ -0,0 +1,35 @@ 
+igt@vc4_create_bo@create-bo-0
+igt@vc4_create_bo@create-bo-4096
+igt@vc4_create_bo@create-bo-zeroed
+igt@vc4_dmabuf_poll@poll-read-waits-until-write-done
+igt@vc4_dmabuf_poll@poll-write-waits-until-write-done
+igt@vc4_label_bo@set-label
+igt@vc4_label_bo@set-bad-handle
+igt@vc4_label_bo@set-bad-name
+igt@vc4_label_bo@set-kernel-name
+igt@vc4_lookup_fail@bad-color-write
+igt@vc4_purgeable_bo@mark-willneed
+igt@vc4_purgeable_bo@mark-purgeable
+igt@vc4_purgeable_bo@mark-purgeable-twice
+igt@vc4_purgeable_bo@access-purgeable-bo-mem
+igt@vc4_purgeable_bo@access-purged-bo-mem
+igt@vc4_purgeable_bo@mark-unpurgeable-check-retained
+igt@vc4_purgeable_bo@mark-unpurgeable-purged
+igt@vc4_purgeable_bo@free-purged-bo
+igt@vc4_tiling@get-bad-handle
+igt@vc4_tiling@set-bad-handle
+igt@vc4_tiling@get-bad-flags
+igt@vc4_tiling@set-bad-flags
+igt@vc4_tiling@get-bad-modifier
+igt@vc4_tiling@set-bad-modifier
+igt@vc4_tiling@set-get
+igt@vc4_tiling@get-after-free
+igt@vc4_wait_bo@bad-bo
+igt@vc4_wait_bo@bad-pad
+igt@vc4_wait_bo@unused-bo-0ns
+igt@vc4_wait_bo@unused-bo-1ns
+igt@vc4_wait_bo@used-bo
+igt@vc4_wait_bo@used-bo-0ns
+igt@vc4_wait_bo@used-bo-1ns
+igt@vc4_wait_seqno@bad-seqno-0ns
+igt@vc4_wait_seqno@bad-seqno-1ns