From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: LGCI Bug Filing <lgci.bug.filing@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_addfb_basic: Skip not relevant subtests for Xe
Date: Thu, 23 Nov 2023 13:03:23 +0000 [thread overview]
Message-ID: <e22f00defcbdb91df9847c397e0c55d8d16a9e0e.camel@intel.com> (raw)
In-Reply-To: <170074113036.8136.9495695269822136438@emeril.freedesktop.org>
[-- Attachment #1: Type: text/plain, Size: 4322 bytes --]
Hello,
Regression reported by CI have nothing to do with my patch. Similar failures are seen already earlier:
http://gfx-ci.igk.intel.com/cibuglog-ng/results/all?query_key=9b320f08684c4d11aa04576ca3f00680be33ddb5
Can you please re-report so I can get also results from shards.
Thank you in advance,
Jouni Högander
On Thu, 2023-11-23 at 12:05 +0000, Patchwork wrote:
Patch Details
Series: tests/kms_addfb_basic: Skip not relevant subtests for Xe
URL: https://patchwork.freedesktop.org/series/126820/
State: failure
Details: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10253/index.html
CI Bug Log - changes from IGT_7598 -> IGTPW_10253
Summary
FAILURE
Serious unknown changes coming with IGTPW_10253 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_10253, please notify your bug team (lgci.bug.filing@intel.com) 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_10253/index.html
Participating hosts (38 -> 36)
Additional (1): bat-kbl-2
Missing (3): bat-mtlp-8 bat-adlp-11 fi-snb-2520m
Possible new issues
Here are the unknown changes that may have been introduced in IGTPW_10253:
IGT changes
Possible regressions
* igt@i915_selftest@live@gt_mocs:
* bat-mtlp-6: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7598/bat-mtlp-6/igt@i915_selftest@live@gt_mocs.html> -> DMESG-WARN<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10253/bat-mtlp-6/igt@i915_selftest@live@gt_mocs.html>
Known issues
Here are the changes found in IGTPW_10253 that come from known issues:
IGT changes
Issues hit
* igt@fbdev@info:
* bat-kbl-2: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10253/bat-kbl-2/igt@fbdev@info.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#1849<https://gitlab.freedesktop.org/drm/intel/issues/1849>)
* igt@gem_lmem_swapping@parallel-random-engines:
* bat-kbl-2: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10253/bat-kbl-2/igt@gem_lmem_swapping@parallel-random-engines.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +20 other tests skip
* igt@kms_hdmi_inject@inject-audio:
* fi-kbl-guc: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7598/fi-kbl-guc/igt@kms_hdmi_inject@inject-audio.html> -> FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10253/fi-kbl-guc/igt@kms_hdmi_inject@inject-audio.html> (IGT#3<https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/3>)
* igt@kms_pipe_crc_basic@read-crc-frame-sequence:
* bat-kbl-2: NOTRUN -> SKIP<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10253/bat-kbl-2/igt@kms_pipe_crc_basic@read-crc-frame-sequence.html> (fdo#109271<https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#1845<https://gitlab.freedesktop.org/drm/intel/issues/1845>) +14 other tests skip
* igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-edp-1:
* bat-rplp-1: PASS<https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7598/bat-rplp-1/igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-edp-1.html> -> ABORT<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10253/bat-rplp-1/igt@kms_pipe_crc_basic@read-crc-frame-sequence@pipe-d-edp-1.html> (i915#8668<https://gitlab.freedesktop.org/drm/intel/issues/8668>)
Possible fixes
* igt@gem_exec_fence@basic-await@rcs0:
* bat-dg2-9: FAIL<https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7598/bat-dg2-9/igt@gem_exec_fence@basic-await@rcs0.html> -> PASS<https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10253/bat-dg2-9/igt@gem_exec_fence@basic-await@rcs0.html>
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
Build changes
* CI: CI-20190529 -> None
* IGT: IGT_7598 -> IGTPW_10253
CI-20190529: 20190529
CI_DRM_13914: 0b1d4056dbe497edc6d866ca5b3f54c5927bd7c0 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_10253: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10253/index.html
IGT_7598: 6be4fb999857e135d54a6643a57dfe394e9c6f2e @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
[-- Attachment #2: Type: text/html, Size: 6029 bytes --]
next prev parent reply other threads:[~2023-11-23 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 10:26 [igt-dev] [PATCH i-g-t v2] tests/kms_addfb_basic: Skip not relevant subtests for Xe Jouni Högander
2023-11-23 12:05 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2023-11-23 13:03 ` Hogander, Jouni [this message]
2023-11-24 8:12 ` Illipilli, TejasreeX
2023-11-23 12:37 ` [igt-dev] [PATCH i-g-t v2] " Juha-Pekka Heikkila
2023-11-23 13:12 ` Kamil Konieczny
2023-11-23 14:40 ` Hogander, Jouni
2023-11-23 13:39 ` [igt-dev] ✓ CI.xeBAT: success for " Patchwork
2023-11-23 16:53 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-11-25 7:18 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=e22f00defcbdb91df9847c397e0c55d8d16a9e0e.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lgci.bug.filing@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