From: Patchwork <patchwork@emeril.freedesktop.org>
To: Petri Latvala <petri.latvala@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t,1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable (rev4)
Date: Mon, 21 Oct 2019 11:42:32 -0000 [thread overview]
Message-ID: <20191021114232.5726.27272@emeril.freedesktop.org> (raw)
In-Reply-To: <20191017091713.25456-1-petri.latvala@intel.com>
== Series Details ==
Series: series starting with [i-g-t,1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable (rev4)
URL : https://patchwork.freedesktop.org/series/68141/
State : warning
== Summary ==
ERROR! This series introduces new undocumented tests:
kms_busy@basic-flip-pipe-A
kms_busy@basic-flip-pipe-B
kms_busy@basic-flip-pipe-C
kms_busy@basic-flip-pipe-D
kms_busy@basic-flip-pipe-E
kms_busy@basic-flip-pipe-F
kms_busy@basic-modeset-pipe-A
kms_busy@basic-modeset-pipe-B
kms_busy@basic-modeset-pipe-C
kms_busy@basic-modeset-pipe-D
kms_busy@basic-modeset-pipe-E
kms_busy@basic-modeset-pipe-F
kms_busy@extended-modeset-hang-newfb-render-pipe-A
kms_busy@extended-modeset-hang-newfb-render-pipe-B
kms_busy@extended-modeset-hang-newfb-render-pipe-C
kms_busy@extended-modeset-hang-newfb-render-pipe-D
kms_busy@extended-modeset-hang-newfb-render-pipe-E
kms_busy@extended-modeset-hang-newfb-render-pipe-F
kms_busy@extended-modeset-hang-newfb-with-reset-render-pipe-A
kms_busy@extended-modeset-hang-newfb-with-reset-render-pipe-B
kms_busy@extended-modeset-hang-newfb-with-reset-render-pipe-C
kms_busy@extended-modeset-hang-newfb-with-reset-render-pipe-D
kms_busy@extended-modeset-hang-newfb-with-reset-render-pipe-E
kms_busy@extended-modeset-hang-newfb-with-reset-render-pipe-F
kms_busy@extended-modeset-hang-oldfb-render-pipe-A
kms_busy@extended-modeset-hang-oldfb-render-pipe-B
kms_busy@extended-modeset-hang-oldfb-render-pipe-C
kms_busy@extended-modeset-hang-oldfb-render-pipe-D
kms_busy@extended-modeset-hang-oldfb-render-pipe-E
kms_busy@extended-modeset-hang-oldfb-render-pipe-F
kms_busy@extended-modeset-hang-oldfb-with-reset-render-pipe-A
kms_busy@extended-modeset-hang-oldfb-with-reset-render-pipe-B
kms_busy@extended-modeset-hang-oldfb-with-reset-render-pipe-C
kms_busy@extended-modeset-hang-oldfb-with-reset-render-pipe-D
kms_busy@extended-modeset-hang-oldfb-with-reset-render-pipe-E
kms_busy@extended-modeset-hang-oldfb-with-reset-render-pipe-F
kms_busy@extended-pageflip-hang-newfb-render-pipe-A
kms_busy@extended-pageflip-hang-newfb-render-pipe-B
kms_busy@extended-pageflip-hang-newfb-render-pipe-C
kms_busy@extended-pageflip-hang-newfb-render-pipe-D
kms_busy@extended-pageflip-hang-newfb-render-pipe-E
kms_busy@extended-pageflip-hang-newfb-render-pipe-F
kms_busy@extended-pageflip-hang-oldfb-render-pipe-A
kms_busy@extended-pageflip-hang-oldfb-render-pipe-B
kms_busy@extended-pageflip-hang-oldfb-render-pipe-C
kms_busy@extended-pageflip-hang-oldfb-render-pipe-D
kms_busy@extended-pageflip-hang-oldfb-render-pipe-E
kms_busy@extended-pageflip-hang-oldfb-render-pipe-F
kms_busy@extended-pageflip-modeset-hang-oldfb-render-pipe-A
kms_busy@extended-pageflip-modeset-hang-oldfb-render-pipe-B
kms_busy@extended-pageflip-modeset-hang-oldfb-render-pipe-C
kms_busy@extended-pageflip-modeset-hang-oldfb-render-pipe-D
kms_busy@extended-pageflip-modeset-hang-oldfb-render-pipe-E
kms_busy@extended-pageflip-modeset-hang-oldfb-render-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/72067 for more details
== Logs ==
For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/72067
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-10-21 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:17 [igt-dev] [PATCH i-g-t 1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable Petri Latvala
2019-10-17 9:17 ` [igt-dev] [PATCH i-g-t 2/2] intel-ci: Adjust pipe-specific blacklisting Petri Latvala
2019-10-17 9:21 ` [igt-dev] [PATCH i-g-t v2 " Petri Latvala
2019-11-07 14:45 ` [igt-dev] [PATCH i-g-t " Arkadiusz Hiler
2019-11-07 14:54 ` Arkadiusz Hiler
2019-10-17 9:41 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t,1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable (rev2) Patchwork
2019-10-17 10:00 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2019-10-20 10:51 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t,1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable (rev3) Patchwork
2019-10-20 11:08 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2019-10-21 11:42 ` Patchwork [this message]
2019-10-21 12:17 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable (rev4) Patchwork
2019-10-21 15:22 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-11-07 14:45 ` [igt-dev] [PATCH i-g-t 1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable Arkadiusz Hiler
2019-11-11 11:31 ` [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/2] kms_busy: Rename tests so pipe-specific subtests are blacklistable (rev4) 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=20191021114232.5726.27272@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@intel.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