Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for series starting with [CI,1/2] drm/i915/skl: Rework MOCS tables to keep common part in a define
Date: Fri, 30 Nov 2018 21:59:17 -0000	[thread overview]
Message-ID: <20181130215917.17614.40083@emeril.freedesktop.org> (raw)
In-Reply-To: <20181130213304.17329-1-lucas.demarchi@intel.com>

== Series Details ==

Series: series starting with [CI,1/2] drm/i915/skl: Rework MOCS tables to keep common part in a define
URL   : https://patchwork.freedesktop.org/series/53337/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_5236 -> Patchwork_10983
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://patchwork.freedesktop.org/api/1.0/series/53337/revisions/1/mbox/

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

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

### IGT changes ###

#### Issues hit ####

  * igt@gem_close_race@basic-threads:
    - fi-bsw-kefka:       PASS -> FAIL [fdo#108656]

  * igt@prime_vgem@basic-fence-flip:
    - fi-ilk-650:         PASS -> FAIL [fdo#104008]

  * {igt@runner@aborted}:
    - {fi-icl-y}:         NOTRUN -> FAIL [fdo#108070]

  
#### Possible fixes ####

  * igt@gem_ctx_create@basic-files:
    - fi-bsw-kefka:       DMESG-FAIL [fdo#108656] -> PASS

  * igt@kms_pipe_crc_basic@read-crc-pipe-a-frame-sequence:
    - fi-byt-clapper:     FAIL [fdo#103191] / [fdo#107362] -> PASS

  * igt@prime_vgem@basic-fence-flip:
    - fi-gdg-551:         DMESG-FAIL [fdo#103182] -> PASS

  
  {name}: This element is suppressed. This means it is ignored when computing
          the status of the difference (SUCCESS, WARNING, or FAILURE).

  [fdo#103182]: https://bugs.freedesktop.org/show_bug.cgi?id=103182
  [fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
  [fdo#104008]: https://bugs.freedesktop.org/show_bug.cgi?id=104008
  [fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
  [fdo#108070]: https://bugs.freedesktop.org/show_bug.cgi?id=108070
  [fdo#108656]: https://bugs.freedesktop.org/show_bug.cgi?id=108656


Participating hosts (48 -> 43)
------------------------------

  Additional (2): fi-icl-y fi-pnv-d510 
  Missing    (7): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-apl-guc fi-ctg-p8600 


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

    * Linux: CI_DRM_5236 -> Patchwork_10983

  CI_DRM_5236: f9cd6a3ffb4400071d46dd123347802c1422d9da @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4736: 285ebfb3b7adc56586031afa5150c4e5ad40c229 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_10983: 9e03c0a762706f4e9d6e0c10c1c4e3f647ba7c13 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

9e03c0a76270 drm/i915/icl: Define MOCS table for Icelake
454290da2817 drm/i915/skl: Rework MOCS tables to keep common part in a define

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10983/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-11-30 21:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30 21:33 [CI 1/2] drm/i915/skl: Rework MOCS tables to keep common part in a define Lucas De Marchi
2018-11-30 21:33 ` [CI 2/2] drm/i915/icl: Define MOCS table for Icelake Lucas De Marchi
2018-11-30 21:59 ` Patchwork [this message]
2018-11-30 21:59 ` [CI 1/2] drm/i915/skl: Rework MOCS tables to keep common part in a define Chris Wilson
2018-11-30 23:19   ` Lucas De Marchi
2018-11-30 23:35     ` Chris Wilson
2018-11-30 23:37       ` Chris Wilson
2018-11-30 23:47       ` Lucas De Marchi
2018-12-01 17:15 ` ✓ Fi.CI.IGT: success for series starting with [CI,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=20181130215917.17614.40083@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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