From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: petri.latvala@intel.com
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for lib: sync i915_pciids.h with kernel (rev7)
Date: Thu, 22 Oct 2020 22:58:02 -0700 [thread overview]
Message-ID: <871rhp7ac5.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <160342116299.1405.324614752786297465@emeril.freedesktop.org>
On Thu, 22 Oct 2020 19:46:02 -0700, Patchwork wrote:
> CI Bug Log - changes from CI_DRM_9187_full -> IGTPW_5086_full
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with IGTPW_5086_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_5086_full, 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/IGTPW_5086/index.html
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in IGTPW_5086_full:
>
> IGT changes
>
> Possible regressions
>
> * igt@gem_userptr_blits@map-fixed-invalidate-busy-gup@uc:
>
> * shard-hsw: PASS -> FAIL
>
> * igt@kms_color@pipe-a-ctm-0-25:
>
> * shard-hsw: PASS -> INCOMPLETE
These are false positives. v8 of the patch in patchwork is the same as v7
and shows no regressions. In reality it is v2 of the patch and is identical
to v1. Thanks.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2020-10-23 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 1:05 [igt-dev] [PATCH i-g-t] lib: sync i915_pciids.h with kernel Ashutosh Dixit
2020-10-23 1:43 ` [igt-dev] ✓ Fi.CI.BAT: success for lib: sync i915_pciids.h with kernel (rev7) Patchwork
2020-10-23 2:46 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-23 5:58 ` Dixit, Ashutosh [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=871rhp7ac5.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@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