Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: <igt-dev@lists.freedesktop.org>, <lgci.bug.filing@intel.com>,
	<saix.nandan.yedireswarapu@intel.com>,
	<tejasreex.illipilli@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.BAT: failure for tests/intel/kms_pm_lpsp: Use lib helper to iterate connector modes
Date: Fri, 24 Nov 2023 12:42:37 +0530	[thread overview]
Message-ID: <7b3666e8-f4f0-425e-84de-5281ff0e3da4@intel.com> (raw)
In-Reply-To: <170080965402.13022.10594470700937754149@emeril.freedesktop.org>

Hello,

Can someone please re-report below false positive?

- Bhanu

On 24-11-2023 12:37 pm, Patchwork wrote:
> *Patch Details*
> *Series:*	tests/intel/kms_pm_lpsp: Use lib helper to iterate connector modes
> *URL:*	https://patchwork.freedesktop.org/series/126853/ 
> <https://patchwork.freedesktop.org/series/126853/>
> *State:*	failure
> *Details:* 
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10259/index.html 
> <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10259/index.html>
> 
> 
>   CI Bug Log - changes from IGT_7601 -> IGTPW_10259
> 
> 
>     Summary
> 
> *FAILURE*
> 
> Serious unknown changes coming with IGTPW_10259 absolutely need to be
> verified manually.
> 
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_10259, 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_10259/index.html
> 
> 
>     Participating hosts (38 -> 35)
> 
> Missing (3): bat-kbl-2 fi-snb-2520m fi-bsw-n3050
> 
> 
>     Possible new issues
> 
> Here are the unknown changes that may have been introduced in IGTPW_10259:
> 
> 
>       IGT changes
> 
> 
>         Possible regressions
> 
>   * igt@i915_selftest@live@gt_heartbeat:
>       o fi-skl-6600u: PASS
>         <https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7601/fi-skl-6600u/igt@i915_selftest@live@gt_heartbeat.html> -> DMESG-FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10259/fi-skl-6600u/igt@i915_selftest@live@gt_heartbeat.html>
> 
> 
>     Known issues
> 
> Here are the changes found in IGTPW_10259 that come from known issues:
> 
> 
>       IGT changes
> 
> 
>         Issues hit
> 
>   * igt@kms_pipe_crc_basic@suspend-read-crc:
>       o bat-rpls-1: NOTRUN -> SKIP
>         <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10259/bat-rpls-1/igt@kms_pipe_crc_basic@suspend-read-crc.html> (i915#1845 <https://gitlab.freedesktop.org/drm/intel/issues/1845>)
> 
> 
>         Possible fixes
> 
>   *
> 
>     igt@gem_exec_suspend@basic-s0@smem:
> 
>       o bat-dg2-9: INCOMPLETE
>         <https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7601/bat-dg2-9/igt@gem_exec_suspend@basic-s0@smem.html> (i915#8797 <https://gitlab.freedesktop.org/drm/intel/issues/8797> / i915#9275 <https://gitlab.freedesktop.org/drm/intel/issues/9275>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10259/bat-dg2-9/igt@gem_exec_suspend@basic-s0@smem.html>
>   *
> 
>     igt@i915_selftest@live@requests:
> 
>       o bat-rpls-1: INCOMPLETE
>         <https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7601/bat-rpls-1/igt@i915_selftest@live@requests.html> -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10259/bat-rpls-1/igt@i915_selftest@live@requests.html>
>   *
> 
>     igt@kms_hdmi_inject@inject-audio:
> 
>       o fi-kbl-guc: FAIL
>         <https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7601/fi-kbl-guc/igt@kms_hdmi_inject@inject-audio.html> (IGT#3 <https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/3>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10259/fi-kbl-guc/igt@kms_hdmi_inject@inject-audio.html>
> 
> 
>     Build changes
> 
>   * CI: CI-20190529 -> None
>   * IGT: IGT_7601 -> IGTPW_10259
> 
> CI-20190529: 20190529
> CI_DRM_13919: 94f973d8238e0d8fd1b0234f220783a1e346f60b @ 
> git://anongit.freedesktop.org/gfx-ci/linux
> IGTPW_10259: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10259/index.html
> IGT_7601: 9c6e7f255724e327627be7c8ed30e23742e97386 @ 
> https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> 

  reply	other threads:[~2023-11-24  7:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24  5:46 [igt-dev] [i-g-t] tests/intel/kms_pm_lpsp: Use lib helper to iterate connector modes Bhanuprakash Modem
2023-11-24  7:07 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2023-11-24  7:12   ` Modem, Bhanuprakash [this message]
2023-11-24  7:15 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-11-26  6:05 ` [igt-dev] ✓ CI.xeBAT: success for tests/intel/kms_pm_lpsp: Use lib helper to iterate connector modes (rev2) Patchwork
2023-11-26  6:15 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-26  8:55 ` [igt-dev] ✗ GitLab.Pipeline: warning for tests/intel/kms_pm_lpsp: Use lib helper to iterate connector modes (rev3) Patchwork
2023-11-26  9:25 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-11-26  9:28 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-11-26 10:47 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-27  5:36 ` [igt-dev] [i-g-t] tests/intel/kms_pm_lpsp: Use lib helper to iterate connector modes Karthik B S

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=7b3666e8-f4f0-425e-84de-5281ff0e3da4@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lgci.bug.filing@intel.com \
    --cc=saix.nandan.yedireswarapu@intel.com \
    --cc=tejasreex.illipilli@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