From: Patchwork <patchwork@emeril.freedesktop.org>
To: Oscar Mateo <oscar.mateo@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: warning for Various improvements around the GuC topic
Date: Tue, 21 Mar 2017 17:42:00 -0000 [thread overview]
Message-ID: <20170321174200.6163.17091@emeril.freedesktop.org> (raw)
In-Reply-To: <1490086977-9282-1-git-send-email-oscar.mateo@intel.com>
== Series Details ==
Series: Various improvements around the GuC topic
URL : https://patchwork.freedesktop.org/series/21624/
State : warning
== Summary ==
Series 21624v1 Various improvements around the GuC topic
https://patchwork.freedesktop.org/api/1.0/series/21624/revisions/1/mbox/
Test gem_exec_flush:
Subgroup basic-batch-kernel-default-uc:
fail -> PASS (fi-snb-2600) fdo#100007
Test gem_exec_suspend:
Subgroup basic-s4-devices:
dmesg-warn -> PASS (fi-bxt-t5700) fdo#100125
Test pm_rpm:
Subgroup basic-pci-d3-state:
pass -> DMESG-WARN (fi-bxt-j4205)
fdo#100007 https://bugs.freedesktop.org/show_bug.cgi?id=100007
fdo#100125 https://bugs.freedesktop.org/show_bug.cgi?id=100125
fi-bdw-5557u total:278 pass:263 dwarn:0 dfail:0 fail:4 skip:11 time: 453s
fi-bsw-n3050 total:278 pass:235 dwarn:0 dfail:0 fail:4 skip:39 time: 554s
fi-bxt-j4205 total:278 pass:254 dwarn:1 dfail:0 fail:4 skip:19 time: 522s
fi-bxt-t5700 total:278 pass:254 dwarn:0 dfail:0 fail:4 skip:20 time: 558s
fi-byt-j1900 total:278 pass:247 dwarn:0 dfail:0 fail:4 skip:27 time: 494s
fi-byt-n2820 total:278 pass:243 dwarn:0 dfail:0 fail:4 skip:31 time: 485s
fi-hsw-4770 total:278 pass:258 dwarn:0 dfail:0 fail:4 skip:16 time: 432s
fi-hsw-4770r total:278 pass:258 dwarn:0 dfail:0 fail:4 skip:16 time: 430s
fi-ilk-650 total:278 pass:228 dwarn:0 dfail:0 fail:4 skip:46 time: 437s
fi-ivb-3520m total:278 pass:256 dwarn:0 dfail:0 fail:4 skip:18 time: 516s
fi-ivb-3770 total:278 pass:256 dwarn:0 dfail:0 fail:4 skip:18 time: 489s
fi-kbl-7500u total:278 pass:256 dwarn:0 dfail:0 fail:4 skip:18 time: 481s
fi-skl-6260u total:278 pass:264 dwarn:0 dfail:0 fail:4 skip:10 time: 469s
fi-skl-6700hq total:278 pass:257 dwarn:0 dfail:0 fail:4 skip:17 time: 590s
fi-skl-6700k total:278 pass:252 dwarn:4 dfail:0 fail:4 skip:18 time: 494s
fi-skl-6770hq total:278 pass:264 dwarn:0 dfail:0 fail:4 skip:10 time: 513s
fi-snb-2520m total:278 pass:246 dwarn:0 dfail:0 fail:4 skip:28 time: 542s
fi-snb-2600 total:278 pass:245 dwarn:0 dfail:0 fail:4 skip:29 time: 412s
7035813558b7d9601c8fdda50498cf9f8d7f0f2b drm-tip: 2017y-03m-21d-15h-58m-46s UTC integration manifest
1b4ed14 drm/i915/guc: Move guc_interrupts_release next to guc_interrupts_capture
b952000 drm/i915/guc: Split out the mmio_white_list struct
b8b653e drm/i915/guc: Refactor the concept "GuC context descriptor" into "GuC stage descriptor"
8ffda10 drm/i915/guc: A little bit more of doorbell sanitization
8f22f65 drm/i915/guc: Wait for doorbell to be inactive before deallocating
1362e1f drm/i915/guc: Improve the GuC documentation & comments about proxy submissions
f3b3a7b drm/i915/guc: Make intel_guc_send a function pointer
68aaede drm/i915/guc: Break out the GuC log extras into their own "runtime" struct
deb97d4 drm/i915/guc: The Additional Data Struct (ADS) should get enabled together with GuC submission
c821db7 drm/i915/guc: Add onion teardown to the GuC setup
3abdc29 drm/i915/guc: Keep the ctx_pool_vaddr mapped, for easy access
96f0f61 drm/i915/guc: Sanitize GuC client initialization
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_4250/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-21 17:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 9:02 [PATCH 00/12] Various improvements around the GuC topic Oscar Mateo
2017-03-21 9:02 ` [PATCH 01/12] drm/i915/guc: Sanitize GuC client initialization Oscar Mateo
2017-03-22 9:28 ` Joonas Lahtinen
2017-03-22 9:46 ` Oscar Mateo
2017-03-21 9:02 ` [PATCH 02/12] drm/i915/guc: Keep the ctx_pool_vaddr mapped, for easy access Oscar Mateo
2017-03-22 9:45 ` Chris Wilson
2017-03-22 9:42 ` Oscar Mateo
2017-03-22 16:57 ` Chris Wilson
2017-03-21 9:02 ` [PATCH 03/12] drm/i915/guc: Add onion teardown to the GuC setup Oscar Mateo
2017-03-21 9:02 ` [PATCH 04/12] drm/i915/guc: The Additional Data Struct (ADS) should get enabled together with GuC submission Oscar Mateo
2017-03-21 17:51 ` Ceraolo Spurio, Daniele
2017-03-21 9:02 ` [PATCH 05/12] drm/i915/guc: Break out the GuC log extras into their own "runtime" struct Oscar Mateo
2017-03-21 9:02 ` [PATCH 06/12] drm/i915/guc: Make intel_guc_send a function pointer Oscar Mateo
2017-03-21 9:02 ` [PATCH 07/12] drm/i915/guc: Improve the GuC documentation & comments about proxy submissions Oscar Mateo
2017-03-21 17:54 ` Ceraolo Spurio, Daniele
2017-03-21 9:02 ` [PATCH 08/12] drm/i915/guc: Wait for doorbell to be inactive before deallocating Oscar Mateo
2017-03-21 18:20 ` Ceraolo Spurio, Daniele
2017-03-21 11:24 ` Oscar Mateo
2017-03-22 9:33 ` Joonas Lahtinen
2017-03-21 9:02 ` [PATCH 09/12] drm/i915/guc: A little bit more of doorbell sanitization Oscar Mateo
2017-03-21 9:02 ` [PATCH 10/12] drm/i915/guc: Refactor the concept "GuC context descriptor" into "GuC stage descriptor" Oscar Mateo
2017-03-22 10:05 ` Joonas Lahtinen
2017-03-21 9:02 ` [PATCH 11/12] drm/i915/guc: Split out the mmio_white_list struct Oscar Mateo
2017-03-21 18:04 ` Ceraolo Spurio, Daniele
2017-03-21 9:02 ` [PATCH 12/12] drm/i915/guc: Move guc_interrupts_release next to guc_interrupts_capture Oscar Mateo
2017-03-21 18:08 ` Ceraolo Spurio, Daniele
2017-03-21 17:42 ` Patchwork [this message]
2017-03-22 10:08 ` ✗ Fi.CI.BAT: warning for Various improvements around the GuC topic Joonas Lahtinen
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=20170321174200.6163.17091@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=oscar.mateo@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;
as well as URLs for NNTP newsgroup(s).