From: Karolina Stolarek <karolina.stolarek@intel.com>
To: <igt-dev@lists.freedesktop.org>
Cc: Sai Nandan Yedireswarapu <saix.nandan.yedireswarapu@intel.com>,
Lakshminarayana Vudum <lakshminarayana.vudum@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests/gem_exercise_blt: Don't allow hangs
Date: Thu, 2 Mar 2023 08:21:02 +0100 [thread overview]
Message-ID: <a602d845-1999-d6e6-e2b2-97492716bb79@intel.com> (raw)
In-Reply-To: <167767879159.6635.4347308063747682758@emeril.freedesktop.org>
On 1.03.2023 14:53, Patchwork wrote:
> *Patch Details*
> *Series:* tests/gem_exercise_blt: Don't allow hangs
> *URL:* https://patchwork.freedesktop.org/series/114513/
> <https://patchwork.freedesktop.org/series/114513/>
> *State:* failure
> *Details:*
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8545/index.html
> <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8545/index.html>
>
>
> CI Bug Log - changes from CI_DRM_12796 -> IGTPW_8545
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with IGTPW_8545 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_8545, 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_8545/index.html
>
>
> Participating hosts (39 -> 38)
>
> Missing (1): fi-snb-2520m
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in IGTPW_8545:
>
>
> IGT changes
>
>
> Possible regressions
>
> *
>
> igt@dmabuf@all-tests@dma_fence:
>
> o fi-cfl-8109u: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12796/fi-cfl-8109u/igt@dmabuf@all-tests@dma_fence.html> -> DMESG-FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8545/fi-cfl-8109u/igt@dmabuf@all-tests@dma_fence.html>
> *
>
> igt@dmabuf@all-tests@sanitycheck:
>
> o fi-cfl-8109u: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12796/fi-cfl-8109u/igt@dmabuf@all-tests@sanitycheck.html> -> ABORT <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8545/fi-cfl-8109u/igt@dmabuf@all-tests@sanitycheck.html>
My changes didn't touch this test, so these failures are not related to
the patch.
All the best,
Karolina
>
> Known issues
>
> Here are the changes found in IGTPW_8545 that come from known issues:
>
>
> IGT changes
>
>
> Issues hit
>
> *
>
> igt@gem_exec_gttfill@basic:
>
> o fi-pnv-d510: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12796/fi-pnv-d510/igt@gem_exec_gttfill@basic.html> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8545/fi-pnv-d510/igt@gem_exec_gttfill@basic.html> (i915#7229 <https://gitlab.freedesktop.org/drm/intel/issues/7229>)
> *
>
> igt@i915_selftest@live@gt_heartbeat:
>
> o fi-apl-guc: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12796/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html> -> DMESG-FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8545/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html> (i915#5334 <https://gitlab.freedesktop.org/drm/intel/issues/5334>)
>
>
> Warnings
>
> * igt@i915_selftest@live@slpc:
> o bat-rpls-1: DMESG-FAIL
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12796/bat-rpls-1/igt@i915_selftest@live@slpc.html> (i915#6367 <https://gitlab.freedesktop.org/drm/intel/issues/6367> / i915#7996 <https://gitlab.freedesktop.org/drm/intel/issues/7996>) -> DMESG-FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8545/bat-rpls-1/igt@i915_selftest@live@slpc.html> (i915#6367 <https://gitlab.freedesktop.org/drm/intel/issues/6367>)
>
>
> Build changes
>
> * CI: CI-20190529 -> None
> * IGT: IGT_7177 -> IGTPW_8545
>
> CI-20190529: 20190529
> CI_DRM_12796: 56c017efe176b9f3ab1700b80d3d20970c851414 @
> git://anongit.freedesktop.org/gfx-ci/linux
> IGTPW_8545: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_8545/index.html
> IGT_7177: 0cdc4a676cd9f9e495ad3ae441ed3322f1e14a88 @
> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>
>
> Testlist changes
>
> -igt@kms_plane_scaling@i915-max-source-size
>
next prev parent reply other threads:[~2023-03-02 7:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 12:09 [igt-dev] [PATCH i-g-t] tests/gem_exercise_blt: Don't allow hangs Karolina Stolarek
2023-03-01 12:25 ` Zbigniew Kempczyński
2023-03-01 13:53 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2023-03-02 7:21 ` Karolina Stolarek [this message]
2023-03-02 8:04 ` Yedireswarapu, SaiX Nandan
2023-03-02 8:00 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-03-03 11:07 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/gem_exercise_blt: Don't allow hangs (rev2) Patchwork
2023-03-03 11:28 ` Karolina Stolarek
2023-03-03 13:00 ` Patchwork
2023-03-06 7:45 ` [igt-dev] ✗ Fi.CI.IGT: failure for tests/gem_exercise_blt: Don't allow hangs Patchwork
2023-03-06 9:33 ` Karolina Stolarek
2023-03-06 9:16 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/gem_exercise_blt: Don't allow hangs (rev2) Patchwork
2023-03-06 9:32 ` Karolina Stolarek
2023-03-07 8:31 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/gem_exercise_blt: Don't allow hangs (rev3) Patchwork
2023-03-07 18:31 ` [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=a602d845-1999-d6e6-e2b2-97492716bb79@intel.com \
--to=karolina.stolarek@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lakshminarayana.vudum@intel.com \
--cc=saix.nandan.yedireswarapu@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