From: Maxime Ripard <mripard@kernel.org>
To: Daniel Vetter <daniel.vetter@intel.com>, David Airlie <airlied@linux.ie>
Cc: Helen Koike <helen.koike@collabora.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/doc: ci: Require more context for flaky tests
Date: Thu, 26 Oct 2023 13:02:27 +0200 [thread overview]
Message-ID: <2cn4lsfadj7qjp3fapeu7z36xvzmuzecqic5vjascb4ybzelqa@izqhugbrzmv2> (raw)
In-Reply-To: <169831792811.896759.18431283797442582804.b4-ty@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
On Thu, Oct 26, 2023 at 12:58:48PM +0200, Maxime Ripard wrote:
> On Thu, 19 Oct 2023 11:46:09 +0200, Maxime Ripard wrote:
> > Flaky tests can be very difficult to reproduce after the facts, which
> > will make it even harder to ever fix.
> >
> > Let's document the metadata we agreed on to provide more context to
> > anyone trying to address these fixes.
> >
> >
> > [...]
>
> Applied to drm/drm-misc (drm-misc-next).
b4 might have been confused, but I only applied the v2.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-10-26 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 9:46 [PATCH] drm/doc: ci: Require more context for flaky tests Maxime Ripard
2023-10-19 10:46 ` Daniel Vetter
2023-10-19 16:51 ` Helen Koike
2023-10-20 4:33 ` Helen Koike
2023-10-23 15:09 ` Maxime Ripard
2023-10-25 12:47 ` Helen Koike
2023-10-25 14:19 ` Maxime Ripard
2023-10-23 15:05 ` Maxime Ripard
2023-10-26 10:58 ` Maxime Ripard
2023-10-26 11:02 ` Maxime Ripard [this message]
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=2cn4lsfadj7qjp3fapeu7z36xvzmuzecqic5vjascb4ybzelqa@izqhugbrzmv2 \
--to=mripard@kernel.org \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=helen.koike@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).