From: Andi Shyti <andi.shyti@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Jonathan Cavitt <jonathan.cavitt@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev3)
Date: Wed, 18 Oct 2023 05:51:34 +0200 [thread overview]
Message-ID: <ZS9WRr1m/3VL5tKN@ashyti-mobl2.lan> (raw)
In-Reply-To: <ZS9Q7hmOBGzz1le7@ashyti-mobl2.lan>
> > Possible regressions
> >
> > • igt@gem_exec_parallel@fds@vcs0:
> >
> > □ shard-tglu: PASS -> INCOMPLETE
> > • igt@gem_exec_parallel@fds@vcs1:
> >
> > □ shard-dg2: PASS -> INCOMPLETE +1 other test incomplete
> > • igt@gem_mmap_offset@clear@lmem0:
> >
> > □ shard-dg1: PASS -> INCOMPLETE
> > • igt@kms_psr@psr2_suspend:
> >
> > □ shard-mtlp: NOTRUN -> FAIL
>
> These failures don't look depending on this series.
>
> The gem_exec_parallel test has been causing some troubles also
> during the test of v16, but it already has some history that
> needs to be looked after[*].
>
> I don't want to start all the chain of tests I did yesterday, so
> that I'm going ahead and merge the series.
besides these failures happen on machines where the patch doesn't
have any effect and in our manual tests we don't see them.
Andi
next prev parent reply other threads:[~2023-10-18 3:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 18:07 [Intel-gfx] [PATCH v17 0/7] drm/i915: Define and use GuC and CTB TLB invalidation routines Jonathan Cavitt
2023-10-17 18:08 ` [Intel-gfx] [PATCH v17 1/7] drm/i915: Add GuC TLB Invalidation device info flags Jonathan Cavitt
2023-10-17 18:08 ` [Intel-gfx] [PATCH v17 2/7] drm/i915/guc: Add CT size delay helper Jonathan Cavitt
2023-10-17 18:08 ` [Intel-gfx] [PATCH v17 3/7] drm/i915: Define and use GuC and CTB TLB invalidation routines Jonathan Cavitt
2023-10-17 18:08 ` [Intel-gfx] [PATCH v17 4/7] drm/i915: No TLB invalidation on suspended GT Jonathan Cavitt
2023-10-17 18:08 ` [Intel-gfx] [PATCH v17 5/7] drm/i915: No TLB invalidation on wedged GT Jonathan Cavitt
2023-10-17 18:08 ` [Intel-gfx] [PATCH v17 6/7] drm/i915/gt: Increase sleep in gt_tlb selftest sanitycheck Jonathan Cavitt
2023-10-17 18:08 ` [Intel-gfx] [PATCH v17 7/7] drm/i915: Enable GuC TLB invalidations for MTL Jonathan Cavitt
2023-10-17 19:07 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines Patchwork
2023-10-17 19:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-17 19:25 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-17 20:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev2) Patchwork
2023-10-17 20:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-17 20:20 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-17 21:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev3) Patchwork
2023-10-17 21:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-17 21:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-18 2:40 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-18 3:28 ` Andi Shyti
2023-10-18 3:51 ` Andi Shyti [this message]
2023-10-18 4:18 ` [Intel-gfx] [PATCH v17 0/7] drm/i915: Define and use GuC and CTB TLB invalidation routines Andi Shyti
-- strict thread matches above, loose matches on Subject: below --
2023-10-16 14:51 [Intel-gfx] [PATCH v16 " Jonathan Cavitt
2023-10-17 5:59 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev3) Patchwork
2023-10-13 22:14 [Intel-gfx] [PATCH v15 0/7] drm/i915: Define and use GuC and CTB TLB invalidation routines Jonathan Cavitt
2023-10-15 22:04 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev3) Patchwork
2023-10-06 18:20 [Intel-gfx] [PATCH v8 0/7] drm/i915: Define and use GuC and CTB TLB invalidation routines Jonathan Cavitt
2023-10-09 14:40 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev3) 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=ZS9WRr1m/3VL5tKN@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=nirmoy.das@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