All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
	Patchwork <patchwork@emeril.freedesktop.org>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: ✓ Fi.CI.BAT: success for drm/i915/pmu: Do not assume fixed hrtimer period (rev3)
Date: Tue, 5 Jun 2018 16:47:55 +0100	[thread overview]
Message-ID: <65f1a67f-4443-c3fb-932e-e13ab6a8ab97@linux.intel.com> (raw)
In-Reply-To: <20180605152345.11690.58947@emeril.freedesktop.org>


On 05/06/2018 16:23, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/i915/pmu: Do not assume fixed hrtimer period (rev3)
> URL   : https://patchwork.freedesktop.org/series/44191/
> State : success
> 
> == Summary ==
> 
> = CI Bug Log - changes from CI_DRM_4279 -> Patchwork_9204 =
> 
> == Summary - WARNING ==
> 
>    Minor unknown changes coming with Patchwork_9204 need to be verified
>    manually.
>    
>    If you think the reported changes have nothing to do with the changes
>    introduced in Patchwork_9204, please notify your bug team to allow them
>    to document this new failure mode, which will reduce false positives in CI.
> 
>    External URL: https://patchwork.freedesktop.org/api/1.0/series/44191/revisions/3/mbox/
> 
> == Possible new issues ==
> 
>    Here are the unknown changes that may have been introduced in Patchwork_9204:
> 
>    === IGT changes ===
> 
>      ==== Warnings ====
> 
>      igt@gem_exec_gttfill@basic:
>        fi-pnv-d510:        PASS -> SKIP
> 
>      
> == Known issues ==
> 
>    Here are the changes found in Patchwork_9204 that come from known issues:
> 
>    === IGT changes ===
> 
>      ==== Issues hit ====
> 
>      igt@drv_module_reload@basic-reload:
>        fi-glk-j4005:       NOTRUN -> DMESG-WARN (fdo#106725, fdo#106248)
> 
>      igt@kms_flip@basic-flip-vs-modeset:
>        fi-glk-j4005:       NOTRUN -> DMESG-WARN (fdo#106000)
> 
>      igt@prime_vgem@basic-write:
>        fi-glk-j4005:       NOTRUN -> DMESG-WARN (fdo#105719)
> 
>      
>      ==== Possible fixes ====
> 
>      igt@gem_mmap_gtt@basic-small-bo-tiledx:
>        fi-gdg-551:         FAIL (fdo#102575) -> PASS
> 
>      
>    fdo#102575 https://bugs.freedesktop.org/show_bug.cgi?id=102575
>    fdo#105719 https://bugs.freedesktop.org/show_bug.cgi?id=105719
>    fdo#106000 https://bugs.freedesktop.org/show_bug.cgi?id=106000
>    fdo#106248 https://bugs.freedesktop.org/show_bug.cgi?id=106248
>    fdo#106725 https://bugs.freedesktop.org/show_bug.cgi?id=106725
> 
> 
> == Participating hosts (39 -> 37) ==
> 
>    Additional (2): fi-glk-j4005 fi-bxt-dsi
>    Missing    (4): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-skl-6700hq
> 
> 
> == Build changes ==
> 
>      * Linux: CI_DRM_4279 -> Patchwork_9204
> 
>    CI_DRM_4279: c17149502fba5d36314b384bbf43b2b9c93292cf @ git://anongit.freedesktop.org/gfx-ci/linux
>    IGT_4507: 938135f033d7fd79c04a7a042d40f9d074489ffd @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>    Patchwork_9204: dc3004b98ee002dfcb9603a962a4ad5e40e46c40 @ git://anongit.freedesktop.org/gfx-ci/linux
> 
> 
> == Linux commits ==
> 
> dc3004b98ee0 drm/i915/pmu: Do not assume fixed hrtimer period

Pushed, thanks for the discovery, ideas and review!

Regards,

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

  reply	other threads:[~2018-06-05 15:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 14:02 [CI] drm/i915/pmu: Do not assume fixed hrtimer period Tvrtko Ursulin
2018-06-05 14:20 ` Chris Wilson
2018-06-05 15:06   ` Tvrtko Ursulin
2018-06-05 15:13     ` Chris Wilson
2018-06-05 15:23 ` ✓ Fi.CI.BAT: success for drm/i915/pmu: Do not assume fixed hrtimer period (rev3) Patchwork
2018-06-05 15:47   ` Tvrtko Ursulin [this message]
2018-06-05 20:28 ` ✓ Fi.CI.IGT: " 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=65f1a67f-4443-c3fb-932e-e13ab6a8ab97@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=patchwork@emeril.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.