public inbox for intel-gfx@lists.freedesktop.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: failure for series starting with [01/10] drm/i915: Rename intel_device_info and accessors
Date: Fri, 09 Feb 2018 21:37:33 -0000	[thread overview]
Message-ID: <20180209213733.20110.55534@emeril.freedesktop.org> (raw)
In-Reply-To: <20180209211654.32043-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [01/10] drm/i915: Rename intel_device_info and accessors
URL   : https://patchwork.freedesktop.org/series/38018/
State : failure

== Summary ==

Series 38018v1 series starting with [01/10] drm/i915: Rename intel_device_info and accessors
https://patchwork.freedesktop.org/api/1.0/series/38018/revisions/1/mbox/

Test core_auth:
        Subgroup basic-auth:
                pass       -> INCOMPLETE (fi-gdg-551)
                pass       -> INCOMPLETE (fi-blb-e6850)
                pass       -> INCOMPLETE (fi-pnv-d510)
                pass       -> INCOMPLETE (fi-bwr-2160)
                pass       -> INCOMPLETE (fi-elk-e7500)
                pass       -> INCOMPLETE (fi-ilk-650)
                pass       -> INCOMPLETE (fi-snb-2520m)
                pass       -> INCOMPLETE (fi-snb-2600)
                pass       -> INCOMPLETE (fi-ivb-3520m)
                pass       -> INCOMPLETE (fi-ivb-3770)
                pass       -> INCOMPLETE (fi-bxt-dsi)
Test debugfs_test:
        Subgroup read_all_entries:
                pass       -> DMESG-WARN (fi-byt-j1900)
                pass       -> DMESG-WARN (fi-byt-n2820)
                pass       -> DMESG-WARN (fi-hsw-4770)
                pass       -> DMESG-WARN (fi-bdw-5557u)
                pass       -> DMESG-WARN (fi-bdw-gvtdvm)
                pass       -> DMESG-WARN (fi-bsw-n3050)
                pass       -> DMESG-WARN (fi-skl-6260u)
                pass       -> DMESG-WARN (fi-skl-6600u)
                pass       -> DMESG-WARN (fi-skl-6700hq)
                pass       -> DMESG-WARN (fi-skl-6700k2)
                pass       -> DMESG-WARN (fi-skl-6770hq)
                pass       -> DMESG-WARN (fi-skl-guc)
                pass       -> DMESG-WARN (fi-skl-gvtdvm)
                pass       -> DMESG-WARN (fi-bxt-j4205)
                pass       -> DMESG-WARN (fi-kbl-7500u)
                pass       -> DMESG-WARN (fi-kbl-7560u)
                pass       -> DMESG-WARN (fi-kbl-r)
                pass       -> DMESG-WARN (fi-glk-1)
                pass       -> DMESG-WARN (fi-cfl-s2)
                pass       -> DMESG-WARN (fi-cnl-y3)
Test gem_busy:
        Subgroup basic-busy-default:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup basic-hang-default:
                pass       -> DMESG-WARN (fi-glk-1)
Test gem_close_race:
        Subgroup basic-process:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup basic-threads:
                pass       -> DMESG-WARN (fi-glk-1)
Test gem_cpu_reloc:
        Subgroup basic:
                pass       -> DMESG-WARN (fi-glk-1)
Test gem_cs_tlb:
        Subgroup basic-default:
                pass       -> DMESG-WARN (fi-glk-1) fdo#104858
Test gem_ctx_create:
        Subgroup basic-files:
                pass       -> DMESG-WARN (fi-glk-1)
Test gem_ctx_exec:
        Subgroup basic:
                pass       -> DMESG-WARN (fi-glk-1)
Test gem_ctx_switch:
        Subgroup basic-default:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup basic-default-heavy:
                pass       -> DMESG-WARN (fi-glk-1)
Test gem_exec_basic:
        Subgroup basic-blt:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup basic-bsd:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup basic-default:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup basic-render:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup basic-vebox:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup gtt-blt:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup gtt-bsd:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup gtt-default:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup gtt-render:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup gtt-vebox:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup readonly-blt:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup readonly-bsd:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup readonly-default:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup readonly-render:
                pass       -> DMESG-WARN (fi-glk-1)
        Subgroup readonly-vebox:
                pass       -> DMESG-WARN (fi-glk-1)
Test gem_exec_create:
        Subgroup basic:
                pass       -> DMESG-WARN (fi-glk-1)
Test gem_exec_fence:
WARNING: Long output truncated

897018779f8b9aeac758688f0fd21169dfe66fdf drm-tip: 2018y-02m-09d-16h-18m-21s UTC integration manifest
e223b4dc1c59 drm/i915: Make a mutable copy of intel_device_static_info.has_fbc
0b2bc5036546 drm/i915: Make a mutable copy of pages_size in intel_driver_caps
7549e33d5c0c drm/i915: Move SSEU runtime info to intel_device_runtime_info
d3ec3ccbd404 drm/i915: Disable dynamic setup of device_info->num_rings
96b0fea9d11f drm/i915: Remove a local writable device_info
64e29a77408a drm/i915: Move PCI-ID from static device info to runtime
9953dee3d8ea drm/i915: Move EDRAM capability bits to intel_device_runtime_info
8a39615857c8 drm/i915: Store platform_mask inside the static device info
3322c4aa98ce drm/i915: Store gen_mask inside the static device info
2b5a0179cc99 drm/i915: Rename intel_device_info and accessors

== Logs ==

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

      parent reply	other threads:[~2018-02-09 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 21:16 [PATCH 01/10] drm/i915: Rename intel_device_info and accessors Chris Wilson
2018-02-09 21:16 ` [PATCH 02/10] drm/i915: Store gen_mask inside the static device info Chris Wilson
2018-02-09 21:16 ` [PATCH 03/10] drm/i915: Store platform_mask " Chris Wilson
2018-02-09 21:16 ` [PATCH 04/10] drm/i915: Move EDRAM capability bits to intel_device_runtime_info Chris Wilson
2018-02-09 21:16 ` [PATCH 05/10] drm/i915: Move PCI-ID from static device info to runtime Chris Wilson
2018-02-09 21:16 ` [PATCH 06/10] drm/i915: Remove a local writable device_info Chris Wilson
2018-02-09 21:16 ` [PATCH 07/10] drm/i915: Disable dynamic setup of device_info->num_rings Chris Wilson
2018-02-09 21:16 ` [PATCH 08/10] drm/i915: Move SSEU runtime info to intel_device_runtime_info Chris Wilson
2018-02-12 16:48   ` Ville Syrjälä
2018-02-09 21:16 ` [PATCH 09/10] drm/i915: Make a mutable copy of pages_size in intel_driver_caps Chris Wilson
2018-02-09 21:16 ` [PATCH 10/10] drm/i915: Make a mutable copy of intel_device_static_info.has_fbc Chris Wilson
2018-02-12 16:50   ` Ville Syrjälä
2018-02-09 21:37 ` Patchwork [this message]

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=20180209213733.20110.55534@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox