All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Sundaresan, Sujaritha" <sujaritha.sundaresan@intel.com>
Subject: Re:  Xe.CI.FULL: failure for drm/xe/guc: Reset GuC before unmapping its post-hwconfig buffers
Date: Tue, 17 Nov 2026 23:14:53 +0000	[thread overview]
Message-ID: <5b7bee71e1d3508db80f301a3a4fcb6c0fff2b6e.camel@intel.com> (raw)
In-Reply-To: <179241172879.39992.11184448398668896772@221881a7231d>

On Mon, 2026-10-19 at 12:08 +0000, Patchwork wrote:
> Patch Details
> Series:	drm/xe/guc: Reset GuC before unmapping its post-hwconfig
> buffers
> URL:	https://patchwork.freedesktop.org/series/176370/
> State:	failure
> Details:	
> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-176370v1/index.html
> ERROR: The runconfig 'xe-5972-
> a9828cc3cc428b3892cde517d3662baa30687dad_FULL' does not exist in the
> database

Maybe good to re-run this just to be safe...

-Stuart

  reply	other threads:[~2026-11-17 23:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 10:04 [PATCH] drm/xe/guc: Reset GuC before unmapping its post-hwconfig buffers Sujaritha Sundaresan
2026-10-19  9:26 ` ✓ CI.KUnit: success for " Patchwork
2026-10-19 10:17 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-19 12:08 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-11-17 23:14   ` Summers, Stuart [this message]
2026-10-26 14:07 ` [PATCH] " Vivekanandan, Balasubramani
2026-11-04  7:37   ` Sundaresan, Sujaritha
2026-11-13 19:51     ` Ceraolo Spurio, Daniele
2026-11-18 14:28       ` Vivekanandan, Balasubramani
2026-11-18  9:47 ` ✗ CI.checkpatch: warning for drm/xe/guc: Reset GuC before unmapping its post-hwconfig buffers (rev2) Patchwork
2026-11-18  9:49 ` ✓ CI.KUnit: success " Patchwork
2026-11-18 10:28 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-18 22:48 ` ✓ Xe.CI.FULL: " 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=5b7bee71e1d3508db80f301a3a4fcb6c0fff2b6e.camel@intel.com \
    --to=stuart.summers@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sujaritha.sundaresan@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 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.