All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✓ Fi.CI.BAT: success for i915: Add gem_exec_endless (rev3)
Date: Tue, 19 May 2020 21:14:41 -0000	[thread overview]
Message-ID: <158992288156.31238.8933420253352185143@emeril.freedesktop.org> (raw)
In-Reply-To: <20200519100217.1761103-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: i915: Add gem_exec_endless (rev3)
URL   : https://patchwork.freedesktop.org/series/72247/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_8506 -> IGTPW_4595
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4595/index.html

Known issues
------------

  Here are the changes found in IGTPW_4595 that come from known issues:

### IGT changes ###

#### Possible fixes ####

  * igt@i915_selftest@live@execlists:
    - fi-kbl-8809g:       [INCOMPLETE][1] ([i915#1874]) -> [PASS][2]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-8809g/igt@i915_selftest@live@execlists.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4595/fi-kbl-8809g/igt@i915_selftest@live@execlists.html

  
  [i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874


Participating hosts (49 -> 42)
------------------------------

  Missing    (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-hsw-4770 fi-byt-clapper fi-bdw-samus 


Build changes
-------------

  * CI: CI-20190529 -> None
  * IGT: IGT_5661 -> IGTPW_4595

  CI-20190529: 20190529
  CI_DRM_8506: d6a73e9084ff6adfabbad014bc294d254484f304 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_4595: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4595/index.html
  IGT_5661: a772a7c7a761c6125bc0af5284ad603478107737 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools



== Testlist changes ==

+igt@gem_exec_endless@dispatch

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4595/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2020-05-19 21:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 10:02 [Intel-gfx] [PATCH i-g-t] i915: Add gem_exec_endless Chris Wilson
2020-05-19 10:02 ` [igt-dev] " Chris Wilson
2020-05-19 10:43 ` [Intel-gfx] " Mika Kuoppala
2020-05-19 10:43   ` [igt-dev] " Mika Kuoppala
2020-05-19 10:47   ` [Intel-gfx] " Chris Wilson
2020-05-19 10:47     ` Chris Wilson
2020-05-19 11:11 ` [igt-dev] ✗ GitLab.Pipeline: failure for i915: Add gem_exec_endless (rev2) Patchwork
2020-05-19 11:28 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-05-19 16:11 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2020-05-19 20:43 ` [Intel-gfx] [PATCH i-g-t] i915: Add gem_exec_endless Chris Wilson
2020-05-19 20:43   ` [igt-dev] " Chris Wilson
2020-05-19 21:05 ` [igt-dev] ✗ GitLab.Pipeline: failure for i915: Add gem_exec_endless (rev3) Patchwork
2020-05-19 21:14 ` Patchwork [this message]
2020-05-20  8:35 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=158992288156.31238.8933420253352185143@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.