public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Lyude Paul <lyude@redhat.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ GitLab.Pipeline: failure for series starting with [i-g-t,1/2] tests/kms_pipe_crc_basic: Use igt_display_require_output_on_pipe() (rev3)
Date: Tue, 24 Mar 2020 19:11:52 -0000	[thread overview]
Message-ID: <158507711233.5748.1001021982554372475@emeril.freedesktop.org> (raw)
In-Reply-To: <20200318004914.236815-1-lyude@redhat.com>

== Series Details ==

Series: series starting with [i-g-t,1/2] tests/kms_pipe_crc_basic: Use igt_display_require_output_on_pipe() (rev3)
URL   : https://patchwork.freedesktop.org/series/74808/
State : failure

== Summary ==

ERROR! This series introduces new undocumented tests:

kms_pipe_crc_basic@disable-crc-after-crtc-pipe-A
kms_pipe_crc_basic@disable-crc-after-crtc-pipe-B
kms_pipe_crc_basic@disable-crc-after-crtc-pipe-C
kms_pipe_crc_basic@disable-crc-after-crtc-pipe-D
kms_pipe_crc_basic@disable-crc-after-crtc-pipe-E
kms_pipe_crc_basic@disable-crc-after-crtc-pipe-F

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

Other than that, pipeline status: SUCCESS.

see https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/123891 for the overview.

== Logs ==

For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/123891
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2020-03-24 19:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  0:49 [igt-dev] [PATCH i-g-t 1/2] tests/kms_pipe_crc_basic: Use igt_display_require_output_on_pipe() Lyude
2020-03-18  0:49 ` [igt-dev] [PATCH i-g-t 2/2] tests/kms_pipe_crc_basic: Add disable-crc-after-crtc-pipe-* tests Lyude
2020-03-18  1:22 ` [igt-dev] ✗ GitLab.Pipeline: failure for series starting with [i-g-t,1/2] tests/kms_pipe_crc_basic: Use igt_display_require_output_on_pipe() Patchwork
2020-03-18  1:43 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-03-18  7:46 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-03-19 17:53 ` [igt-dev] ✗ GitLab.Pipeline: failure for series starting with [i-g-t,1/2] tests/kms_pipe_crc_basic: Use igt_display_require_output_on_pipe() (rev2) Patchwork
2020-03-19 18:06 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-03-19 20:35 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-03-24 19:11 ` Patchwork [this message]
2020-03-24 19:20 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] tests/kms_pipe_crc_basic: Use igt_display_require_output_on_pipe() (rev3) Patchwork
2020-03-24 20:18 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

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=158507711233.5748.1001021982554372475@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lyude@redhat.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