From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Kempczynski, Zbigniew" <zbigniew.kempczynski@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for Add no-reloc path in gem_sync
Date: Tue, 2 Nov 2021 16:00:48 +0000 [thread overview]
Message-ID: <c1d08e1bbffe41aba5025a843ed34441@intel.com> (raw)
In-Reply-To: <20211102095139.GA10324@zkempczy-mobl2>
We have a bug for the regression, I have updated the filter to include the below test
https://gitlab.freedesktop.org/drm/intel/-/issues/4301
Few tests - fail - *ERROR* flip_done timed out, *ERROR* commit wait timed out
Lakshmi.
-----Original Message-----
From: Kempczynski, Zbigniew <zbigniew.kempczynski@intel.com>
Sent: Tuesday, November 2, 2021 3:52 AM
To: igt-dev@lists.freedesktop.org
Cc: Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for Add no-reloc path in gem_sync
On Tue, Nov 02, 2021 at 09:22:56AM +0000, Patchwork wrote:
> Patch Details
>
> Series: Add no-reloc path in gem_sync
> URL: https://patchwork.freedesktop.org/series/96486/
> State: failure
> Details: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6368/index.html
>
> CI Bug Log - changes from CI_DRM_10826 -> IGTPW_6368
>
> Summary
>
> FAILURE
>
> Serious unknown changes coming with IGTPW_6368 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_6368, 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_6368/index.html
>
> Participating hosts (40 -> 32)
>
> Additional (1): fi-pnv-d510
> Missing (9): fi-kbl-soraka fi-cml-u2 bat-dg1-6 fi-bsw-n3050 fi-hsw-4200u
> fi-bsw-cyan bat-adlp-4 fi-elk-e7500 fi-bsw-kefka
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in IGTPW_6368:
>
> IGT changes
>
> Possible regressions
>
> * igt@core_auth@basic-auth:
> * fi-kbl-8809g: PASS -> FAIL
Not related, I've changed gem_sync only.
--
Zbigniew
>
> Known issues
>
> Here are the changes found in IGTPW_6368 that come from known issues:
>
> IGT changes
>
> Issues hit
>
> * igt@gem_exec_suspend@basic-s3:
>
> * fi-tgl-1115g4: PASS -> FAIL (i915#1888)
> * igt@prime_vgem@basic-userptr:
>
> * fi-pnv-d510: NOTRUN -> SKIP (fdo#109271) +53 similar issues
> * igt@runner@aborted:
>
> * fi-kbl-8809g: NOTRUN -> FAIL (i915#3363 / i915#4312)
>
> * fi-bdw-5557u: NOTRUN -> FAIL (i915#1602 / i915#2426 / i915#4312)
>
> Possible fixes
>
> * igt@gem_exec_suspend@basic-s3:
>
> * fi-bdw-5557u: INCOMPLETE (i915#146) -> PASS
> * igt@i915_selftest@live@gem_contexts:
>
> * fi-icl-u2: DMESG-WARN -> PASS +1 similar issue
> * igt@i915_selftest@live@objects:
>
> * fi-icl-u2: DMESG-WARN (i915#2867) -> PASS +2 similar issues
>
> Build changes
>
> * CI: CI-20190529 -> None
> * IGT: IGT_6266 -> IGTPW_6368
>
> CI-20190529: 20190529
> CI_DRM_10826: 8b8fbc1dc64274b9eed192df4bfaeced03bdf0ae @
> git://anongit.freedesktop.org/gfx-ci/linux
> IGTPW_6368: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6368/index.html
> IGT_6266: fa0291675a7a3ade6c219cc52fceac9a0a4a63d8 @
> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
next prev parent reply other threads:[~2021-11-02 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 8:39 [igt-dev] [PATCH i-g-t 0/1] Add no-reloc path in gem_sync Zbigniew Kempczyński
2021-11-02 8:39 ` [igt-dev] [PATCH i-g-t 1/1] tests/gem_sync: Use softpin path for no-reloc gens Zbigniew Kempczyński
2021-11-02 19:40 ` Dixit, Ashutosh
2021-11-03 7:51 ` Zbigniew Kempczyński
2021-11-02 9:22 ` [igt-dev] ✗ Fi.CI.BAT: failure for Add no-reloc path in gem_sync Patchwork
2021-11-02 9:51 ` Zbigniew Kempczyński
2021-11-02 16:00 ` Vudum, Lakshminarayana [this message]
2021-11-02 13:44 ` [igt-dev] ✓ Fi.CI.BAT: success for Add no-reloc path in gem_sync (rev2) Patchwork
2021-11-02 16:08 ` [igt-dev] ✓ Fi.CI.IGT: " 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=c1d08e1bbffe41aba5025a843ed34441@intel.com \
--to=lakshminarayana.vudum@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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.