All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Auld" <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/dg1: Compute MEM Bandwidth using MCHBAR
Date: Thu, 24 Jun 2021 11:04:45 -0000	[thread overview]
Message-ID: <162453268531.1852.10027077712141863437@emeril.freedesktop.org> (raw)
In-Reply-To: <20210624083113.365039-1-matthew.auld@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 2281 bytes --]

== Series Details ==

Series: series starting with [1/2] drm/i915/dg1: Compute MEM Bandwidth using MCHBAR
URL   : https://patchwork.freedesktop.org/series/91848/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_10273 -> Patchwork_20451
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

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

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

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

### IGT changes ###

#### Issues hit ####

  * igt@amdgpu/amd_cs_nop@sync-fork-compute0:
    - fi-kbl-soraka:      NOTRUN -> [SKIP][1] ([fdo#109271]) +9 similar issues
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20451/fi-kbl-soraka/igt@amdgpu/amd_cs_nop@sync-fork-compute0.html

  * igt@i915_selftest@live@hangcheck:
    - fi-icl-y:           [PASS][2] -> [INCOMPLETE][3] ([i915#2782])
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10273/fi-icl-y/igt@i915_selftest@live@hangcheck.html
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20451/fi-icl-y/igt@i915_selftest@live@hangcheck.html

  * igt@runner@aborted:
    - fi-icl-y:           NOTRUN -> [FAIL][4] ([i915#2782])
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20451/fi-icl-y/igt@runner@aborted.html

  
  [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
  [i915#2782]: https://gitlab.freedesktop.org/drm/intel/issues/2782


Participating hosts (40 -> 37)
------------------------------

  Missing    (3): fi-skl-guc fi-bsw-cyan fi-bdw-samus 


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

  * Linux: CI_DRM_10273 -> Patchwork_20451

  CI-20190529: 20190529
  CI_DRM_10273: 7e8fb717a07aaf86771e709855436312f546965b @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_6117: 3ba0a02404f243d6d8f232c6215163cc4b0fd699 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  Patchwork_20451: 9ce7776ed8c0b023dd9725fa5db6fe039704a5ba @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

9ce7776ed8c0 drm/i915/dg1: Double memory bandwidth available
3c3f748f9977 drm/i915/dg1: Compute MEM Bandwidth using MCHBAR

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20451/index.html

[-- Attachment #1.2: Type: text/html, Size: 3011 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2021-06-24 11:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24  8:31 [Intel-gfx] [PATCH 1/2] drm/i915/dg1: Compute MEM Bandwidth using MCHBAR Matthew Auld
2021-06-24  8:31 ` [Intel-gfx] [PATCH 2/2] drm/i915/dg1: Double memory bandwidth available Matthew Auld
2021-06-24 11:04 ` Patchwork [this message]
2021-06-24 14:50 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915/dg1: Compute MEM Bandwidth using MCHBAR Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2021-06-18 16:13 [Intel-gfx] [PATCH 1/2] " Matthew Auld
2021-06-18 19:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] " 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=162453268531.1852.10027077712141863437@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@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 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.