From: Andi Shyti <andi.shyti@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Introduce multitile support
Date: Fri, 18 Mar 2022 10:17:56 +0200 [thread overview]
Message-ID: <YjRANNv09keROx9t@intel.intel> (raw)
In-Reply-To: <164758234860.31587.1988393489717053112@emeril.freedesktop.org>
> • igt@i915_selftest@mock@requests:
>
> □ shard-kbl: PASS -> DMESG-FAIL
>
> □ shard-tglb: PASS -> DMESG-FAIL
>
> □ shard-apl: PASS -> DMESG-FAIL
>
> □ shard-glk: PASS -> DMESG-FAIL
>
> □ shard-skl: PASS -> DMESG-FAIL
>
> □ shard-snb: PASS -> DMESG-FAIL
>
> □ shard-iclb: PASS -> DMESG-FAIL
I don't see how these failures can be related to the series I
sent.
Maybe a false positive?
Andi
next prev parent reply other threads:[~2022-03-18 8:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 2:10 [Intel-gfx] [PATCH v6 0/7] Introduce multitile support Andi Shyti
2022-03-18 2:10 ` Andi Shyti
2022-03-18 2:10 ` [Intel-gfx] [PATCH v6 1/7] drm/i915: Rename INTEL_REGION_LMEM with INTEL_REGION_LMEM_0 Andi Shyti
2022-03-18 2:10 ` Andi Shyti
2022-03-18 2:10 ` [Intel-gfx] [PATCH v6 2/7] drm/i915/gt: add gt_is_root() helper Andi Shyti
2022-03-18 2:10 ` Andi Shyti
2022-03-18 2:10 ` [Intel-gfx] [PATCH v6 3/7] drm/i915: Prepare for multiple GTs Andi Shyti
2022-03-18 2:10 ` Andi Shyti
2022-03-18 13:04 ` [Intel-gfx] " Andrzej Hajda
2022-03-18 2:10 ` [Intel-gfx] [PATCH v6 4/7] drm/i915/gt: create per-tile sysfs interface Andi Shyti
2022-03-18 2:10 ` Andi Shyti
2022-03-18 13:19 ` [Intel-gfx] " Matthew Auld
2022-03-18 13:19 ` Matthew Auld
2022-03-18 14:01 ` [Intel-gfx] " Andi Shyti
2022-03-18 14:01 ` Andi Shyti
2022-03-18 15:00 ` [Intel-gfx] " Andrzej Hajda
2022-03-18 2:10 ` [Intel-gfx] [PATCH v6 5/7] drm/i915/gt: Create per-tile RC6 " Andi Shyti
2022-03-18 2:10 ` Andi Shyti
2022-03-18 2:10 ` [Intel-gfx] [PATCH v6 6/7] drm/i915/gt: Create per-tile RPS sysfs interfaces Andi Shyti
2022-03-18 2:10 ` Andi Shyti
2022-03-18 14:54 ` [Intel-gfx] " Andrzej Hajda
2022-03-18 2:10 ` [Intel-gfx] [PATCH v6 7/7] drm/i915/gt: Adding new sysfs frequency attributes Andi Shyti
2022-03-18 2:10 ` Andi Shyti
2022-03-18 13:09 ` [Intel-gfx] " Andrzej Hajda
2022-03-18 3:07 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce multitile support Patchwork
2022-03-18 3:08 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-18 3:43 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-18 5:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-18 8:17 ` Andi Shyti [this message]
2022-03-18 13:25 ` Matthew Auld
2022-03-18 13:51 ` Tvrtko Ursulin
2022-03-18 14:26 ` Andi Shyti
-- strict thread matches above, loose matches on Subject: below --
2022-03-18 23:39 [Intel-gfx] [PATCH v7 0/7] " Andi Shyti
2022-03-19 2:06 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2022-03-21 10:05 ` Matthew Auld
2022-03-21 16:44 ` Vudum, Lakshminarayana
2022-03-18 22:46 [Intel-gfx] [PATCH v6 0/7] " Andi Shyti
2022-03-19 1:09 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2022-01-17 19:32 [Intel-gfx] [PATCH v4 0/2] " Andi Shyti
2022-01-17 21:32 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2022-01-17 15:09 [Intel-gfx] [PATCH v3 0/2] " Andi Shyti
2022-01-17 17:57 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2022-01-11 12:15 [Intel-gfx] [PATCH 0/2] " Andi Shyti
2022-01-11 21:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " 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=YjRANNv09keROx9t@intel.intel \
--to=andi.shyti@linux.intel.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 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.