From: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ GitLab.Pipeline: failure for Add support for testing writeback connectors (rev2)
Date: Wed, 6 May 2020 18:56:48 -0400 [thread overview]
Message-ID: <20200506225648.caze2q3brlmkmknx@smtp.gmail.com> (raw)
In-Reply-To: <20200504115659.bdp7faed46cfalux@ahiler-desk1.fi.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1394 bytes --]
On 05/04, Arkadiusz Hiler wrote:
> On Fri, Apr 24, 2020 at 01:51:12AM +0000, Patchwork wrote:
> > == Series Details ==
> >
> > Series: Add support for testing writeback connectors (rev2)
> > URL : https://patchwork.freedesktop.org/series/68352/
> > State : failure
> >
> > == Summary ==
> >
> > ERROR! This series introduces new undocumented tests:
> >
> > kms_writeback
> >
> > Can you document them as per the requirement in the [CONTRIBUTING.md]?
> >
> > [Documentation] has more details on how to do this.
> >
> > Here are few examples:
> > https://gitlab.freedesktop.org/drm/igt-gpu-tools/commit/0316695d03aa46108296b27f3982ec93200c7a6e
> > https://gitlab.freedesktop.org/drm/igt-gpu-tools/commit/443cc658e1e6b492ee17bf4f4d891029eb7a205d
> >
> > Thanks in advance!
> >
> > [CONTRIBUTING.md]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/blob/master/CONTRIBUTING.md#L19
> > [Documentation]: https://drm.pages.freedesktop.org/igt-gpu-tools/igt-gpu-tools-Core.html#igt-describe
>
> Hey Rodrigo,
>
> Can you add short test descriptions as explained above?
Hi Arek,
I'm going to add a brief description in the next version. Now, I'm
trying to understand why this series breaks read_all_entries_display_off
and read_all_entries_display_on on i915.
Best Regards
> --
> Cheers,
> Arek
--
Rodrigo Siqueira
https://siqueira.tech
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-05-06 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 1:26 [igt-dev] [PATCH i-g-t v8 0/4] Add support for testing writeback connectors Rodrigo Siqueira
2020-04-24 1:26 ` [igt-dev] [PATCH i-g-t v8 1/4] lib/igt_kms: Add writeback support Rodrigo Siqueira
2020-04-24 1:26 ` [igt-dev] [PATCH i-g-t v8 2/4] kms_writeback: Add initial writeback tests Rodrigo Siqueira
2020-04-24 1:26 ` [igt-dev] [PATCH i-g-t v8 3/4] lib: Add function to hash a framebuffer Rodrigo Siqueira
2020-04-24 1:26 ` [igt-dev] [PATCH i-g-t v8 4/4] kms_writeback: Add writeback-check-output Rodrigo Siqueira
2020-04-24 1:51 ` [igt-dev] ✗ GitLab.Pipeline: failure for Add support for testing writeback connectors (rev2) Patchwork
2020-05-04 11:56 ` Arkadiusz Hiler
2020-05-06 22:56 ` Rodrigo Siqueira [this message]
2020-04-24 2:02 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-04-24 4:39 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-04-29 15:37 ` [Intel-gfx] [PATCH i-g-t v8 0/4] Add support for testing writeback connectors 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=20200506225648.caze2q3brlmkmknx@smtp.gmail.com \
--to=rodrigosiqueiramelo@gmail.com \
--cc=arkadiusz.hiler@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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