From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, ",
Lakshminarayana Vudum" <lakshminarayana.vudum@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gem: Fix the mman selftest (rev2)
Date: Tue, 31 Aug 2021 15:29:21 +0200 [thread overview]
Message-ID: <0ad4df77-b0f6-8782-be2f-7235199b3165@linux.intel.com> (raw)
In-Reply-To: <163041595730.10657.17383745822852397722@emeril.freedesktop.org>
[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]
On 8/31/21 3:19 PM, Patchwork wrote:
> Project List - Patchwork *Patch Details*
> *Series:* drm/i915/gem: Fix the mman selftest (rev2)
> *URL:* https://patchwork.freedesktop.org/series/94062/
> <https://patchwork.freedesktop.org/series/94062/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20928/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20928/index.html>
>
>
> CI Bug Log - changes from CI_DRM_10539 -> Patchwork_20928
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with Patchwork_20928 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_20928, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives
> in CI.
>
> External URL:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20928/index.html
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in
> Patchwork_20928:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b:
> o fi-rkl-guc: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10539/fi-rkl-guc/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b.html>
> -> SKIP
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20928/fi-rkl-guc/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-b.html>
>
>
Lakshmi, this failure is unrelated.
Thanks,
Thomas
[-- Attachment #2: Type: text/html, Size: 3008 bytes --]
next prev parent reply other threads:[~2021-08-31 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 12:29 [Intel-gfx] [PATCH v2] drm/i915/gem: Fix the mman selftest Thomas Hellström
2021-08-31 13:19 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gem: Fix the mman selftest (rev2) Patchwork
2021-08-31 13:29 ` Thomas Hellström [this message]
2021-08-31 16:03 ` Vudum, Lakshminarayana
2021-08-31 15:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-31 18:51 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-09-01 8:33 ` Thomas Hellström
2021-09-01 9:33 ` Thomas Hellström
2021-09-01 12:12 ` Kattamanchi, JaswanthX
2021-09-01 12:06 ` [Intel-gfx] ✓ Fi.CI.IGT: success " 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=0ad4df77-b0f6-8782-be2f-7235199b3165@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lakshminarayana.vudum@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