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: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.BAT: success for drm/i915/guc: Propagate the fw xfer timeout
Date: Wed, 17 Oct 2018 21:12:19 -0000	[thread overview]
Message-ID: <20181017211219.4415.87792@emeril.freedesktop.org> (raw)
In-Reply-To: <20181017202902.16138-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: drm/i915/guc: Propagate the fw xfer timeout
URL   : https://patchwork.freedesktop.org/series/51140/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_5000 -> Patchwork_10495 =

== Summary - SUCCESS ==

  No regressions found.

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

== Known issues ==

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

  === IGT changes ===

    ==== Issues hit ====

    igt@kms_flip@basic-flip-vs-dpms:
      fi-skl-6700hq:      PASS -> DMESG-WARN (fdo#105998)

    igt@kms_frontbuffer_tracking@basic:
      fi-icl-u2:          PASS -> FAIL (fdo#103167)

    
    ==== Possible fixes ====

    igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b:
      fi-byt-clapper:     FAIL (fdo#107362) -> PASS

    
  fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
  fdo#105998 https://bugs.freedesktop.org/show_bug.cgi?id=105998
  fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362


== Participating hosts (47 -> 38) ==

  Missing    (9): fi-kbl-soraka fi-ilk-m540 fi-icl-u fi-hsw-4200u fi-byt-j1900 fi-byt-squawks fi-bsw-cyan fi-pnv-d510 fi-kbl-7560u 


== Build changes ==

    * Linux: CI_DRM_5000 -> Patchwork_10495

  CI_DRM_5000: b9543c130d4f6edd76ec98090c46044ba6d9493e @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4683: 7766b1e2348b32cc8ed58a972c6fd53b20279549 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_10495: c4abf98c4adb62eb18f400a2fb498477e6864af3 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

c4abf98c4adb drm/i915/guc: Propagate the fw xfer timeout

== Logs ==

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

  reply	other threads:[~2018-10-17 21:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 20:29 [PATCH] drm/i915/guc: Propagate the fw xfer timeout Chris Wilson
2018-10-17 21:12 ` Patchwork [this message]
2018-10-17 22:14 ` ✓ Fi.CI.IGT: success for " Patchwork
2018-10-17 23:09 ` [PATCH] " Daniele Ceraolo Spurio
2018-10-17 23:22   ` Michal Wajdeczko
2018-10-18  9:13     ` Chris Wilson
2018-10-18 18:18       ` Daniele Ceraolo Spurio
2018-10-18 18:27         ` Michal Wajdeczko
2018-10-18 19:42           ` Chris Wilson
2018-10-18 19:54 ` [PATCH v2] " Chris Wilson
2018-10-18 19:55 ` [PATCH v3] " Chris Wilson
2018-10-18 20:48   ` Daniele Ceraolo Spurio
2018-10-23  8:50     ` Chris Wilson
2018-10-23 16:04       ` Daniele Ceraolo Spurio
2018-10-18 20:16 ` ✗ Fi.CI.BAT: failure for drm/i915/guc: Propagate the fw xfer timeout (rev2) Patchwork
2018-10-18 20:37 ` ✓ Fi.CI.BAT: success for drm/i915/guc: Propagate the fw xfer timeout (rev3) Patchwork
2018-10-18 23:41 ` ✗ Fi.CI.IGT: failure " 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=20181017211219.4415.87792@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@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.