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 series starting with [i-g-t,1/5] i915: Start putting the mmio_base to wider use
Date: Fri, 28 Feb 2020 11:15:13 -0000 [thread overview]
Message-ID: <158288851352.7475.6325193241529905464@emeril.freedesktop.org> (raw)
In-Reply-To: <20200228104340.2895082-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [i-g-t,1/5] i915: Start putting the mmio_base to wider use
URL : https://patchwork.freedesktop.org/series/74073/
State : failure
== Summary ==
ERROR! This series introduces new undocumented tests:
sysfs_heartbeat_interval
sysfs_heartbeat_interval@idempotent
sysfs_heartbeat_interval@invalid
sysfs_heartbeat_interval@long
sysfs_heartbeat_interval@mixed
sysfs_heartbeat_interval@nopreempt
sysfs_heartbeat_interval@off
sysfs_heartbeat_interval@precise
sysfs_preempt_timeout
sysfs_preempt_timeout@idempotent
sysfs_preempt_timeout@invalid
sysfs_preempt_timeout@off
sysfs_preempt_timeout@timeout
sysfs_timeslice_duration
sysfs_timeslice_duration@duration
sysfs_timeslice_duration@idempotent
sysfs_timeslice_duration@invalid
sysfs_timeslice_duration@off
sysfs_timeslice_duration@timeout
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/113849 for the overview.
== Logs ==
For more details see: https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/pipelines/113849
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-02-28 11:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 10:43 [Intel-gfx] [PATCH i-g-t 1/5] i915: Start putting the mmio_base to wider use Chris Wilson
2020-02-28 10:43 ` [igt-dev] " Chris Wilson
2020-02-28 10:43 ` [Intel-gfx] [PATCH i-g-t 2/5] i915/gem_ctx_isolation: Check engine relative registers Chris Wilson
2020-02-28 19:46 ` Stimson, Dale B
2020-02-28 19:46 ` [igt-dev] " Stimson, Dale B
2020-02-28 10:43 ` [Intel-gfx] [PATCH i-g-t 3/5] i915: Exercise preemption timeout controls in sysfs Chris Wilson
2020-02-28 10:43 ` [igt-dev] " Chris Wilson
2020-02-28 23:27 ` [Intel-gfx] " Andi Shyti
2020-02-28 23:32 ` Chris Wilson
2020-02-28 23:32 ` [igt-dev] " Chris Wilson
2020-02-28 23:51 ` Andi Shyti
2020-02-29 10:21 ` Chris Wilson
2020-02-29 10:21 ` [igt-dev] " Chris Wilson
2020-02-29 12:45 ` Andi Shyti
2020-02-29 18:34 ` Chris Wilson
2020-02-29 18:34 ` [igt-dev] " Chris Wilson
2020-02-29 18:39 ` Chris Wilson
2020-02-28 10:43 ` [Intel-gfx] [PATCH i-g-t 4/5] i915: Exercise sysfs heartbeat controls Chris Wilson
2020-02-28 23:34 ` Andi Shyti
2020-02-28 23:37 ` Chris Wilson
2020-02-28 23:37 ` [igt-dev] " Chris Wilson
2020-02-28 10:43 ` [Intel-gfx] [PATCH i-g-t 5/5] i915: Exercise timeslice sysfs property Chris Wilson
2020-02-28 10:43 ` [igt-dev] " Chris Wilson
2020-02-28 11:15 ` Patchwork [this message]
2020-02-28 11:52 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/5] i915: Start putting the mmio_base to wider use Patchwork
2020-02-28 19:45 ` [Intel-gfx] [igt-dev] [PATCH i-g-t 1/5] " Stimson, Dale B
2020-02-28 19:45 ` Stimson, Dale B
2020-02-28 21:27 ` [Intel-gfx] " Andi Shyti
2020-02-28 21:27 ` [igt-dev] " Andi Shyti
2020-03-01 1:09 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/5] " 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=158288851352.7475.6325193241529905464@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.