intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Fredrik Schön" <fredrikschon@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✓ Fi.CI.IGT: success for Increase LSPCON timeout
Date: Tue, 14 Aug 2018 16:08:53 -0000	[thread overview]
Message-ID: <20180814160853.27608.3992@emeril.freedesktop.org> (raw)
In-Reply-To: <20180813175133.24910-1-fredrik.schon@gmail.com>

== Series Details ==

Series: Increase LSPCON timeout
URL   : https://patchwork.freedesktop.org/series/48183/
State : success

== Summary ==

= CI Bug Log - changes from CI_DRM_4665_full -> Patchwork_9937_full =

== Summary - SUCCESS ==

  No regressions found.

  

== Known issues ==

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

  === IGT changes ===

    ==== Issues hit ====

    igt@gem_workarounds@suspend-resume:
      shard-glk:          NOTRUN -> FAIL (fdo#103375)

    igt@kms_setmode@basic:
      shard-apl:          PASS -> FAIL (fdo#99912)

    
    ==== Possible fixes ====

    igt@drv_suspend@shrink:
      shard-glk:          INCOMPLETE (fdo#106886, k.org#198133, fdo#103359) -> PASS

    igt@gem_workarounds@suspend-resume:
      shard-apl:          FAIL (fdo#103375) -> PASS

    
  fdo#103359 https://bugs.freedesktop.org/show_bug.cgi?id=103359
  fdo#103375 https://bugs.freedesktop.org/show_bug.cgi?id=103375
  fdo#106886 https://bugs.freedesktop.org/show_bug.cgi?id=106886
  fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
  k.org#198133 https://bugzilla.kernel.org/show_bug.cgi?id=198133


== Participating hosts (5 -> 5) ==

  No changes in participating hosts


== Build changes ==

    * Linux: CI_DRM_4665 -> Patchwork_9937

  CI_DRM_4665: 3a43bf5efa33be9f88d70427dbfba4db4377eaf6 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_4594: b0263e5d0563a81a42cf66e7d3b84662d3222862 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
  Patchwork_9937: 977c85e40247ce7d9dc570748f6bbea3473bad75 @ git://anongit.freedesktop.org/gfx-ci/linux
  piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit

== Logs ==

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

  parent reply	other threads:[~2018-08-14 16:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 17:51 [PATCH] [drm][i915] Increase LSPCON timeout Fredrik Schön
2018-08-14 13:09 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-08-14 16:08 ` Patchwork [this message]
2018-08-15 22:39 ` [PATCH] [drm][i915] " Rodrigo Vivi
2018-08-15 22:45   ` Rodrigo Vivi
2018-08-16  7:17     ` Jani Nikula
2018-08-16  7:33       ` Sharma, Shashank
2018-08-16  7:43         ` Chris Wilson
2018-08-16  8:15           ` Sharma, Shashank
2018-08-16  8:36             ` Fredrik Schön
2018-08-16 18:23               ` Rodrigo Vivi
2018-08-16 21:35                 ` fredrikschon
2018-08-16 21:43                   ` Rodrigo Vivi
2018-08-16 21:51                     ` Fredrik Schön
2018-08-16 21:58                       ` Rodrigo Vivi
2018-08-16  9:53       ` Saarinen, Jani

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=20180814160853.27608.3992@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=fredrikschon@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).