dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Tomeu Vizoso <tomeu.vizoso@collabora.com>
To: Rob Clark <robdclark@gmail.com>
Cc: freedreno <freedreno@lists.freedesktop.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Jonathan Corbet <corbet@lwn.net>, David Airlie <airlied@linux.ie>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	linux-doc@vger.kernel.org,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Sean Paul <sean@poorly.run>
Subject: Re: [RFC v3] drm/msm: Add initial ci/ subdirectory
Date: Wed, 11 May 2022 16:03:51 +0200	[thread overview]
Message-ID: <3e4198de-a0be-aa76-c5ea-fd07d47704ee@collabora.com> (raw)
In-Reply-To: <CAF6AEGts6cKOrmRruo8uSXSW=Kq58VZxdPuS13Q7jVajbvga-g@mail.gmail.com>

On 5/11/22 3:20 PM, Rob Clark wrote:
> On Tue, May 10, 2022 at 11:15 PM Tomeu Vizoso
> <tomeu.vizoso@collabora.com> wrote:
>>
>> And use it to store expectations about what the drm/msm driver is
>> supposed to pass in the IGT test suite.
>>
>> Also include a configuration file that points to the out-of-tree CI
>> scripts.
>>
>> By storing the test expectations along the code we can make sure both
>> stay in sync with each other, and so we can know when a code change
>> breaks those expectations.
>>
>> This will allow all contributors to drm/msm to reuse the infrastructure
>> already in gitlab.freedesktop.org to test the driver on several
>> generations of the hardware.
>>
>> v2:
>>    - Fix names of result expectation files to match SoC
>>    - Don't execute tests that are going to skip on all boards
>>
>> v3:
>>    - Remove tracking of dmesg output during test execution
>>
>> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
>> ---
>>   Documentation/gpu/msm_automated_testing.rst   |  70 +++++++++
>>   drivers/gpu/drm/msm/ci/gitlab-ci.yml          |  11 ++
>>   drivers/gpu/drm/msm/ci/msm.testlist           | 144 ++++++++++++++++++
>>   .../gpu/drm/msm/ci/msm_apq8016_results.txt    | 141 +++++++++++++++++
>>   .../gpu/drm/msm/ci/msm_apq8096_results.txt    | 141 +++++++++++++++++
>>   drivers/gpu/drm/msm/ci/msm_sc7180_results.txt | 142 +++++++++++++++++
>>   drivers/gpu/drm/msm/ci/msm_sdm845_results.txt | 142 +++++++++++++++++
>>   7 files changed, 791 insertions(+)
>>   create mode 100644 Documentation/gpu/msm_automated_testing.rst
>>   create mode 100644 drivers/gpu/drm/msm/ci/gitlab-ci.yml
>>   create mode 100644 drivers/gpu/drm/msm/ci/msm.testlist
>>   create mode 100644 drivers/gpu/drm/msm/ci/msm_apq8016_results.txt
>>   create mode 100644 drivers/gpu/drm/msm/ci/msm_apq8096_results.txt
>>   create mode 100644 drivers/gpu/drm/msm/ci/msm_sc7180_results.txt
>>   create mode 100644 drivers/gpu/drm/msm/ci/msm_sdm845_results.txt
>>
> 
> [snip]
> 
>> diff --git a/drivers/gpu/drm/msm/ci/gitlab-ci.yml b/drivers/gpu/drm/msm/ci/gitlab-ci.yml
>> new file mode 100644
>> index 000000000000..9b7caa7fcab2
>> --- /dev/null
>> +++ b/drivers/gpu/drm/msm/ci/gitlab-ci.yml
>> @@ -0,0 +1,11 @@
>> +variables:
>> +  # Change this to use your fork of drm-ci
>> +  DRM_CI_PROJECT_PATH: &drm-ci-project-path gfx-ci/drm-ci
>> +  DRM_CI_COMMIT_SHA: &drm-ci-commit-sha msm
> 
> btw, shouldn't we list an exact commit sha (or tag) for drm-ci, or am
> I overlooking something?  We want to be able to uprev the drm-ci
> version (and therefore igt version) in sync with any necessary updates
> to the expectations

You are right, that was me being lazy and using a branch name to not 
have to update this every time.

But this should better be a commit sha or tag. Will do it on v4.

Cheers,

Tomeu

  reply	other threads:[~2022-05-11 14:03 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  7:01 [RFC] drm/msm: Add initial ci/ subdirectory Tomeu Vizoso
2022-05-10 14:13 ` [RFC v2] " Tomeu Vizoso
2022-05-10 19:39   ` [Freedreno] " Jessica Zhang
2022-05-10 20:25     ` Rob Clark
2022-05-11 17:12       ` Daniel Vetter
2022-05-11 17:46         ` Rob Clark
2022-05-11 19:14           ` Daniel Vetter
2022-05-11 20:32             ` Rob Clark
2022-05-11 21:09               ` Daniel Vetter
2022-05-12 13:28           ` Tomeu Vizoso
2022-05-12 14:02             ` Daniel Vetter
2022-05-11  4:25     ` Tomeu Vizoso
2022-05-11  5:06   ` Adding CI results to the kernel tree was " Dave Airlie
2022-05-11  6:22     ` Greg Kroah-Hartman
2022-05-11 10:26       ` Michel Dänzer
2022-05-11 11:50         ` Greg Kroah-Hartman
2022-05-11 13:33           ` [Freedreno] " Rob Clark
2022-05-11 16:43             ` Daniel Vetter
2022-05-11 17:23               ` Rob Clark
2022-05-12  2:24             ` Theodore Ts'o
2022-05-11 17:33     ` Linus Torvalds
2022-05-11 18:39       ` Rob Clark
2022-05-11 19:08         ` Linus Torvalds
2022-05-11 19:12           ` Linus Torvalds
2022-05-11 20:14             ` [Freedreno] " Rob Clark
2022-05-11 20:06           ` Rob Clark
2022-05-11 19:39       ` Daniel Vetter
2022-05-11  6:15   ` [RFC v3] " Tomeu Vizoso
2022-05-11 13:20     ` Rob Clark
2022-05-11 14:03       ` Tomeu Vizoso [this message]
2022-05-17  8:16     ` [RFC v4] drm: " Tomeu Vizoso
2022-05-17  9:18       ` Neil Armstrong
2022-05-17  9:24         ` Tomeu Vizoso
2022-07-26 18:16       ` [PATCH v5] " Tomeu Vizoso
2022-07-29 15:43         ` Rob Clark
2022-08-10 18:24         ` Rodrigo Siqueira Jordao
2022-08-10 22:08           ` Rob Clark
2022-08-11 10:10           ` Tomeu Vizoso
2022-08-16 15:37         ` [PATCH v6] " Tomeu Vizoso
2022-08-29  9:31           ` [PATCH v7] " Tomeu Vizoso
2022-09-09 14:15             ` [PATCH v8] " Tomeu Vizoso
2022-09-09 17:16               ` Daniel Stone
2022-10-25  7:32                 ` Daniel Vetter
2022-10-25 15:06                   ` Daniel Stone
2022-09-12  7:29               ` [PATCH v9] " Tomeu Vizoso
2022-10-14 17:10                 ` Rob Clark
2022-10-24 22:06                 ` Jessica Zhang
2022-05-11 14:26 ` [RFC] drm/msm: " Jani Nikula
2022-05-11 14:41   ` Rob Clark

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=3e4198de-a0be-aa76-c5ea-fd07d47704ee@collabora.com \
    --to=tomeu.vizoso@collabora.com \
    --cc=airlied@linux.ie \
    --cc=corbet@lwn.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    --cc=tzimmermann@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).