Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Latvala, Petri" <petri.latvala@intel.com>,
	"Kempczynski, Zbigniew" <zbigniew.kempczynski@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/2] lib/intel_batchbuffer: Prepare batch to use in allocator infrastructure
Date: Thu, 1 Oct 2020 07:20:32 +0000	[thread overview]
Message-ID: <3185510192ce44d08bce73c1a5a7ab30@intel.com> (raw)
In-Reply-To: <20201001064836.GZ7444@platvala-desk.ger.corp.intel.com>

Re-reported.

-----Original Message-----
From: Petri Latvala <petri.latvala@intel.com> 
Sent: Wednesday, September 30, 2020 11:49 PM
To: Kempczynski, Zbigniew <zbigniew.kempczynski@intel.com>; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/2] lib/intel_batchbuffer: Prepare batch to use in allocator infrastructure

On Thu, Oct 01, 2020 at 07:28:24AM +0200, Zbigniew Kempczyński wrote:
> On Wed, Sep 30, 2020 at 05:13:00PM +0000, Patchwork wrote:
> >    Patch Details
> > 
> >    Series:  series starting with [i-g-t,1/2] lib/intel_batchbuffer: Prepare   
> >             batch to use in allocator infrastructure                          
> >    URL:     https://patchwork.freedesktop.org/series/82257/                   
> >    State:   failure                                                           
> >    Details: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5032/index.html    
> > 
> >            CI Bug Log - changes from IGT_5794_full -> IGTPW_5032_full
> > 
> > Summary
> > 
> >    FAILURE
> > 
> >    Serious unknown changes coming with IGTPW_5032_full absolutely need to be
> >    verified manually.
> > 
> >    If you think the reported changes have nothing to do with the changes
> >    introduced in IGTPW_5032_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_5032/index.html
> > 
> > Possible new issues
> > 
> >    Here are the unknown changes that may have been introduced in
> >    IGTPW_5032_full:
> > 
> >   IGT changes
> > 
> >     Possible regressions
> > 
> >      * igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@c-edp1:
> >           * shard-iclb: PASS -> INCOMPLETE
> 
> Series don't touch above and it is unrelated to above.

Yep. One for you, Lakshmi.


-- 
Petri Latvala



> 
> --
> Zbigniew
> 
> > 
> > Known issues
> > 
> >    Here are the changes found in IGTPW_5032_full that come from known issues:
> > 
> >   IGT changes
> > 
> >     Issues hit
> > 
> >      * igt@gem_eio@kms:
> > 
> >           * shard-snb: PASS -> DMESG-WARN (i915#1982)
> >      * igt@gem_exec_reloc@basic-many-active@rcs0:
> > 
> >           * shard-apl: PASS -> FAIL (i915#1635 / i915#2389)
> >      * igt@gem_exec_whisper@basic-queues-priority:
> > 
> >           * shard-glk: PASS -> DMESG-WARN (i915#118 / i915#95)
> >      * igt@i915_pm_dc@dc6-psr:
> > 
> >           * shard-iclb: PASS -> FAIL (i915#454)
> >      * igt@i915_suspend@debugfs-reader:
> > 
> >           * shard-kbl: PASS -> DMESG-WARN (i915#180)
> >      * igt@kms_big_fb@x-tiled-64bpp-rotate-0:
> > 
> >           * shard-iclb: PASS -> DMESG-WARN (i915#1982)
> >      * igt@kms_flip@flip-vs-suspend-interruptible@b-vga1:
> > 
> >           * shard-snb: PASS -> DMESG-WARN (i915#42)
> >      * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-onoff:
> > 
> >           * shard-tglb: PASS -> DMESG-WARN (i915#1982) +5 similar issues
> >      * igt@kms_psr@psr2_cursor_blt:
> > 
> >           * shard-iclb: PASS -> SKIP (fdo#109441) +2 similar issues
> >      * igt@kms_setmode@basic:
> > 
> >           * shard-apl: PASS -> FAIL (i915#1635 / i915#31)
> > 
> >     Possible fixes
> > 
> >      * {igt@core_hotunplug@unbind-rebind}:
> > 
> >           * shard-tglb: INCOMPLETE (i915#1602) -> PASS
> > 
> >           * shard-iclb: INCOMPLETE -> PASS
> > 
> >      * igt@feature_discovery@psr2:
> > 
> >           * shard-iclb: SKIP (i915#658) -> PASS
> >      * igt@gem_exec_nop@basic-parallel:
> > 
> >           * shard-glk: DMESG-WARN (i915#118 / i915#95) -> PASS +1 similar
> >             issue
> >      * igt@kms_color@pipe-b-legacy-gamma:
> > 
> >           * shard-kbl: FAIL (i915#71) -> PASS
> > 
> >           * shard-apl: FAIL (i915#1635 / i915#71) -> PASS
> > 
> >      * igt@kms_cursor_crc@pipe-c-cursor-64x64-onscreen:
> > 
> >           * shard-kbl: DMESG-WARN (i915#78) -> PASS
> >      * igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
> > 
> >           * shard-kbl: DMESG-WARN (i915#180) -> PASS +4 similar issues
> >      * igt@kms_flip@modeset-vs-vblank-race@a-hdmi-a1:
> > 
> >           * shard-glk: FAIL (i915#407) -> PASS
> >      * igt@kms_frontbuffer_tracking@fbc-stridechange:
> > 
> >           * shard-tglb: DMESG-WARN (i915#1982) -> PASS +1 similar issue
> > 
> >           * shard-glk: DMESG-WARN (i915#1982) -> PASS
> > 
> >      * igt@kms_psr@psr2_cursor_plane_move:
> > 
> >           * shard-iclb: SKIP (fdo#109441) -> PASS
> >      * igt@kms_setmode@basic:
> > 
> >           * shard-glk: FAIL (i915#31) -> PASS
> >      * igt@perf_pmu@busy-hang@vecs0:
> > 
> >           * shard-iclb: DMESG-WARN (i915#1982) -> PASS
> >      * igt@sysfs_heartbeat_interval@mixed@bcs0:
> > 
> >           * shard-kbl: INCOMPLETE (i915#1731) -> PASS
> > 
> >     Warnings
> > 
> >      * igt@i915_pm_dc@dc3co-vpb-simulation:
> > 
> >           * shard-tglb: DMESG-WARN (i915#2411) -> SKIP (i915#1904)
> >      * igt@kms_content_protection@atomic-dpms:
> > 
> >           * shard-apl: TIMEOUT (i915#1319 / i915#1635 / i915#1958) -> FAIL
> >             (fdo#110321 / fdo#110336 / i915#1635)
> >      * igt@kms_frontbuffer_tracking@psr-suspend:
> > 
> >           * shard-tglb: DMESG-WARN (i915#2411) -> DMESG-WARN (i915#1982 /
> >             i915#2411)
> > 
> >    {name}: This element is suppressed. This means it is ignored when
> >    computing
> >    the status of the difference (SUCCESS, WARNING, or FAILURE).
> > 
> > Participating hosts (8 -> 8)
> > 
> >    No changes in participating hosts
> > 
> > Build changes
> > 
> >      * CI: CI-20190529 -> None
> >      * IGT: IGT_5794 -> IGTPW_5032
> > 
> >    CI-20190529: 20190529
> >    CI_DRM_9077: ae1f3f7de609df105aeceed2655656ffc838d720 @
> >    git://anongit.freedesktop.org/gfx-ci/linux
> >    IGTPW_5032: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5032/index.html
> >    IGT_5794: eeccb2a17453f90ad92d1ab6f81ad7d344119d72 @
> >    git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-10-01  7:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 12:09 [igt-dev] [PATCH i-g-t 1/2] lib/intel_batchbuffer: Prepare batch to use in allocator infrastructure Zbigniew Kempczyński
2020-09-30 12:09 ` [igt-dev] [PATCH i-g-t 2/2] lib + tests: Remove possibility to use other than intel_bb context Zbigniew Kempczyński
2020-09-30 13:20 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] lib/intel_batchbuffer: Prepare batch to use in allocator infrastructure Patchwork
2020-09-30 17:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-01  5:28   ` Zbigniew Kempczyński
2020-10-01  6:48     ` Petri Latvala
2020-10-01  7:20       ` Vudum, Lakshminarayana [this message]
2020-10-01  7:19 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=3185510192ce44d08bce73c1a5a7ab30@intel.com \
    --to=lakshminarayana.vudum@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox