From: Maxime Ripard <mripard@kernel.org>
To: Helen Koike <helen.koike@collabora.com>
Cc: David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@intel.com>,
Vignesh Raman <vignesh.raman@collabora.com>,
dri-devel@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH] drm/doc: ci: Require more context for flaky tests
Date: Wed, 25 Oct 2023 16:19:39 +0200 [thread overview]
Message-ID: <5mhwzpeamncih6oorkdq44ub7msqatssg5w5f6y5bdjpy7mgf5@5jernjke5ypf> (raw)
In-Reply-To: <4d2362d8-d88b-4878-8d1a-f54458ebfc9b@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Wed, Oct 25, 2023 at 09:47:07AM -0300, Helen Koike wrote:
> > > > > + # Version: 6.6-rc1
> > > > > + # Failure Rate: 100
> > >
> > > Maybe also:
> > >
> > > # Pipeline url:
> > > https://gitlab.freedesktop.org/helen.fornazier/linux/-/pipelines/1014435
> >
> > Sounds like a good idea yeah :) Are those artifacts archived/deleted at
> > some point or do they stick around forever?
>
> Good point, I asked the admins, they stick for 4 weeks (could be more, but
> it is not forever) :(
That's not even a release cycle :/
I guess it's too short to be useful. We can definitely revisit if that
delay is extended at some point though.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-25 14:19 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 [this message]
2023-10-23 15:05 ` Maxime Ripard
2023-10-26 10:58 ` Maxime Ripard
2023-10-26 11:02 ` Maxime Ripard
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=5mhwzpeamncih6oorkdq44ub7msqatssg5w5f6y5bdjpy7mgf5@5jernjke5ypf \
--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 \
--cc=vignesh.raman@collabora.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 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).