From: Linus Torvalds <torvalds@linux-foundation.org>
To: Rob Clark <robdclark@gmail.com>
Cc: Dave Airlie <airlied@gmail.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel@ffwll.ch>, Jonathan Corbet <corbet@lwn.net>,
Sean Paul <sean@poorly.run>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
freedreno <freedreno@lists.freedesktop.org>
Subject: Re: Adding CI results to the kernel tree was Re: [RFC v2] drm/msm: Add initial ci/ subdirectory
Date: Wed, 11 May 2022 12:08:03 -0700 [thread overview]
Message-ID: <CAHk-=wjbE0f2AGroB1Hy=fx2fh7cRpS0wNdB46Ybk14Mb0b5Jw@mail.gmail.com> (raw)
In-Reply-To: <CAF6AEGusO9XAqHNatJLgV+wpVoyyLg1vHtUsnSkAxJeV7n3WNg@mail.gmail.com>
On Wed, May 11, 2022 at 11:40 AM Rob Clark <robdclark@gmail.com> wrote:
>
> It is missing in this revision of the RFC, but the intention is to
> have the gitlab-ci.yml point to a specific commit SHA in the
> gfx-ci/drm-ci[1] tree, to solve the problem of keeping the results in
> sync with the expectations. Ie. a kernel commit would control moving
> to a new version of i-g-t (and eventually deqp and/or piglit), and at
> the same time make any necessary updates in the expectations files.
Wouldn't it then be better to just have the expectation files in the
ci tree too?
The kernel tree might have just the expected *failures* listed, if
there are any. Presumably the ci tree has to have the expected results
anyway, so what's the advantage of listing non-failures?
Linus
next prev parent reply other threads:[~2022-05-11 19:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220510070140.45407-1-tomeu.vizoso@collabora.com>
2022-05-10 14:13 ` [RFC v2] drm/msm: Add initial ci/ subdirectory 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 [this message]
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
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='CAHk-=wjbE0f2AGroB1Hy=fx2fh7cRpS0wNdB46Ybk14Mb0b5Jw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=tomeu.vizoso@collabora.com \
--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).