From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Latvala, Petri" <petri.latvala@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Prepare error capture for asynchronous migration
Date: Tue, 2 Nov 2021 17:50:12 +0000 [thread overview]
Message-ID: <7f7570cd26ef46af82d9f881cc5c55fa@intel.com> (raw)
In-Reply-To: <4767cf8b-7c53-72fe-a781-1d7223ab6e50@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]
We don’t have the test in our db “spec@arb_gpu_shader5@texturegather@fs-r-0-unorm-2darray”. So, I cannot really address this issue.
FYI @Latvala, Petri<mailto:petri.latvala@intel.com>
From: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Sent: Tuesday, November 2, 2021 9:29 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Prepare error capture for asynchronous migration
On 11/2/21 17:02, Patchwork wrote:
Patch Details
Series:
drm/i915: Prepare error capture for asynchronous migration
URL:
https://patchwork.freedesktop.org/series/96493/
State:
failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/index.html
CI Bug Log - changes from CI_DRM_10827_full -> Patchwork_21503_full
Summary
FAILURE
Serious unknown changes coming with Patchwork_21503_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_21503_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Participating hosts (10 -> 10)
No changes in participating hosts
Possible new issues
Here are the unknown changes that may have been introduced in Patchwork_21503_full:
Piglit changes
Possible regressions
* spec@arb_gpu_shader5@texturegather@fs-r-0-unorm-2darray (NEW):
* pig-kbl-iris: NOTRUN -> INCOMPLETE<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21503/pig-kbl-iris/spec@arb_gpu_shader5@texturegather@fs-r-0-unorm-2darray.html> +5 similar issues
Lakshmi, This failure is unrelated.
Thanks,
Thomas
[-- Attachment #2: Type: text/html, Size: 9676 bytes --]
prev parent reply other threads:[~2021-11-02 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 10:28 [Intel-gfx] [PATCH v5 0/3] drm/i915: Prepare error capture for asynchronous migration Thomas Hellström
2021-11-02 10:28 ` Thomas Hellström
2021-11-02 10:28 ` [Intel-gfx] [PATCH v5 1/3] drm/i915: Update error capture code to avoid using the current vma state Thomas Hellström
2021-11-02 10:28 ` Thomas Hellström
2021-11-02 10:28 ` [Intel-gfx] [PATCH v5 2/3] drm/i915: Use __GFP_KSWAPD_RECLAIM in the capture code Thomas Hellström
2021-11-02 10:28 ` Thomas Hellström
2021-11-02 10:28 ` [Intel-gfx] [PATCH v5 3/3] drm/i915: Initial introduction of vma resources Thomas Hellström
2021-11-02 10:28 ` Thomas Hellström
2021-11-02 12:21 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Prepare error capture for asynchronous migration Patchwork
2021-11-02 12:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-02 16:02 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-02 16:28 ` Thomas Hellström
2021-11-02 17:50 ` Vudum, Lakshminarayana [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=7f7570cd26ef46af82d9f881cc5c55fa@intel.com \
--to=lakshminarayana.vudum@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
--cc=thomas.hellstrom@linux.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.