From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ GitLab.Pipeline: failure for i915/gem_huc_copy: Enable a HuC copy test
Date: Thu, 11 Jun 2020 08:26:02 -0000 [thread overview]
Message-ID: <159186396298.22714.5237779874397644234@emeril.freedesktop.org> (raw)
In-Reply-To: <20200606090858.2137564-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: i915/gem_huc_copy: Enable a HuC copy test
URL : https://patchwork.freedesktop.org/series/78063/
State : failure
== Summary ==
ERROR! This series introduces new undocumented tests:
gem_exec_balancer@bonded-dual
gem_exec_balancer@bonded-pair
gem_exec_balancer@bonded-sync
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/157044 for the overview.
== Logs ==
For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/157044
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2020-06-11 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 9:08 [igt-dev] [CI] i915/gem_huc_copy: Enable a HuC copy test Chris Wilson
2020-06-06 10:09 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-06-06 11:44 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2020-06-11 8:26 ` Patchwork [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=159186396298.22714.5237779874397644234@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.