From: Anshuman Gupta <anshuman.gupta@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Jeevan B <jeevan.b@intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for Add a new IGT test to validate DC3CO state. (rev3)
Date: Wed, 2 Oct 2019 15:02:02 +0530 [thread overview]
Message-ID: <20191002093202.GA29793@intel.com> (raw)
In-Reply-To: <20191001175857.21994.88590@emeril.freedesktop.org>
On 2019-10-01 at 17:58:57 +0000, Patchwork wrote:
> == Series Details ==
>
> Series: Add a new IGT test to validate DC3CO state. (rev3)
> URL : https://patchwork.freedesktop.org/series/66648/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_6982_full -> IGTPW_3518_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with IGTPW_3518_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_3518_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_3518/index.html
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in IGTPW_3518_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * {igt@i915_pm_dc@dc3co-vpb-simulation} (NEW):
> - shard-iclb: NOTRUN -> [SKIP][1]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb8/igt@i915_pm_dc@dc3co-vpb-simulation.html
>
>
> New tests
> ---------
>
> New tests have been introduced between CI_DRM_6982_full and IGTPW_3518_full:
>
> ### New IGT tests (1) ###
>
> * igt@i915_pm_dc@dc3co-vpb-simulation:
> - Statuses : 6 skip(s)
> - Exec time: [0.0] s
Hi Jeevan,
There is no single run on TGL for DC3CO igt test.
Could you please add this test to tests/intel-ci/fast-feedback.testlist list, then it will cover TGL platforms in CI.
You can add simply a line igt@i915_pm_dc@dc3co-vpb-simulation in tests/intel-ci/fast-feedback.testlist and create a patch with DO_NOT_MERGE tag, and send along with this series.
Thanks,
Anshuman Gupta.
>
>
>
> Known issues
> ------------
>
> Here are the changes found in IGTPW_3518_full that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@gem_ctx_isolation@rcs0-s3:
> - shard-apl: [PASS][2] -> [DMESG-WARN][3] ([fdo#108566]) +3 similar issues
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-apl2/igt@gem_ctx_isolation@rcs0-s3.html
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-apl1/igt@gem_ctx_isolation@rcs0-s3.html
>
> * igt@gem_exec_schedule@out-order-bsd2:
> - shard-iclb: [PASS][4] -> [SKIP][5] ([fdo#109276]) +10 similar issues
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb2/igt@gem_exec_schedule@out-order-bsd2.html
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb7/igt@gem_exec_schedule@out-order-bsd2.html
>
> * igt@gem_exec_schedule@reorder-wide-bsd:
> - shard-iclb: [PASS][6] -> [SKIP][7] ([fdo#111325]) +2 similar issues
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb7/igt@gem_exec_schedule@reorder-wide-bsd.html
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb1/igt@gem_exec_schedule@reorder-wide-bsd.html
>
> * igt@gem_userptr_blits@coherency-sync:
> - shard-snb: [PASS][8] -> [DMESG-WARN][9] ([fdo#111870]) +2 similar issues
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-snb5/igt@gem_userptr_blits@coherency-sync.html
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-snb5/igt@gem_userptr_blits@coherency-sync.html
>
> * igt@gem_userptr_blits@dmabuf-sync:
> - shard-kbl: [PASS][10] -> [DMESG-WARN][11] ([fdo#111870]) +2 similar issues
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-kbl1/igt@gem_userptr_blits@dmabuf-sync.html
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-kbl2/igt@gem_userptr_blits@dmabuf-sync.html
>
> * igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup:
> - shard-iclb: [PASS][12] -> [DMESG-WARN][13] ([fdo#111870]) +1 similar issue
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb3/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
> - shard-hsw: [PASS][14] -> [DMESG-WARN][15] ([fdo#111870])
> [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-hsw4/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
> [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-hsw4/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
>
> * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-gtt:
> - shard-iclb: [PASS][16] -> [FAIL][17] ([fdo#103167]) +2 similar issues
> [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-gtt.html
> [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-mmap-gtt.html
>
> * igt@kms_plane_cursor@pipe-a-primary-size-128:
> - shard-hsw: [PASS][18] -> [INCOMPLETE][19] ([fdo#103540]) +1 similar issue
> [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-hsw7/igt@kms_plane_cursor@pipe-a-primary-size-128.html
> [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-hsw8/igt@kms_plane_cursor@pipe-a-primary-size-128.html
>
> * igt@kms_plane_lowres@pipe-a-tiling-x:
> - shard-iclb: [PASS][20] -> [FAIL][21] ([fdo#103166])
> [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb3/igt@kms_plane_lowres@pipe-a-tiling-x.html
> [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb1/igt@kms_plane_lowres@pipe-a-tiling-x.html
>
> * igt@kms_psr@psr2_primary_mmap_gtt:
> - shard-iclb: [PASS][22] -> [SKIP][23] ([fdo#109441]) +1 similar issue
> [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb2/igt@kms_psr@psr2_primary_mmap_gtt.html
> [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb3/igt@kms_psr@psr2_primary_mmap_gtt.html
>
>
> #### Possible fixes ####
>
> * igt@gem_exec_schedule@preemptive-hang-bsd:
> - shard-iclb: [SKIP][24] ([fdo#111325]) -> [PASS][25] +8 similar issues
> [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb1/igt@gem_exec_schedule@preemptive-hang-bsd.html
> [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb3/igt@gem_exec_schedule@preemptive-hang-bsd.html
>
> * igt@gem_tiled_swapping@non-threaded:
> - shard-kbl: [DMESG-WARN][26] ([fdo#108686]) -> [PASS][27]
> [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-kbl6/igt@gem_tiled_swapping@non-threaded.html
> [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-kbl3/igt@gem_tiled_swapping@non-threaded.html
>
> * igt@gem_userptr_blits@coherency-sync:
> - shard-hsw: [DMESG-WARN][28] ([fdo#111870]) -> [PASS][29] +3 similar issues
> [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-hsw7/igt@gem_userptr_blits@coherency-sync.html
> [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-hsw1/igt@gem_userptr_blits@coherency-sync.html
>
> * igt@gem_userptr_blits@map-fixed-invalidate-busy:
> - shard-snb: [DMESG-WARN][30] ([fdo#111870]) -> [PASS][31] +2 similar issues
> [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-snb2/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
> [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-snb6/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
> - shard-kbl: [DMESG-WARN][32] ([fdo#111870]) -> [PASS][33] +2 similar issues
> [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-kbl1/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
> [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-kbl7/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
>
> * igt@gem_userptr_blits@sync-unmap-after-close:
> - shard-apl: [DMESG-WARN][34] ([fdo#109385] / [fdo#111870]) -> [PASS][35]
> [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-apl7/igt@gem_userptr_blits@sync-unmap-after-close.html
> [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-apl4/igt@gem_userptr_blits@sync-unmap-after-close.html
>
> * igt@gem_userptr_blits@sync-unmap-cycles:
> - shard-glk: [DMESG-WARN][36] ([fdo#111870]) -> [PASS][37] +2 similar issues
> [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-glk2/igt@gem_userptr_blits@sync-unmap-cycles.html
> [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-glk7/igt@gem_userptr_blits@sync-unmap-cycles.html
>
> * igt@i915_suspend@sysfs-reader:
> - shard-apl: [DMESG-WARN][38] ([fdo#108566]) -> [PASS][39] +2 similar issues
> [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-apl7/igt@i915_suspend@sysfs-reader.html
> [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-apl6/igt@i915_suspend@sysfs-reader.html
> - shard-kbl: [INCOMPLETE][40] ([fdo#103665] / [fdo#108767]) -> [PASS][41]
> [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-kbl3/igt@i915_suspend@sysfs-reader.html
> [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-kbl1/igt@i915_suspend@sysfs-reader.html
>
> * igt@kms_flip@dpms-vs-vblank-race-interruptible:
> - shard-iclb: [INCOMPLETE][42] ([fdo#107713]) -> [PASS][43] +1 similar issue
> [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb7/igt@kms_flip@dpms-vs-vblank-race-interruptible.html
> [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb6/igt@kms_flip@dpms-vs-vblank-race-interruptible.html
>
> * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render:
> - shard-iclb: [FAIL][44] ([fdo#103167]) -> [PASS][45] +8 similar issues
> [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render.html
> [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb6/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-render.html
>
> * igt@kms_psr@psr2_cursor_mmap_cpu:
> - shard-iclb: [SKIP][46] ([fdo#109441]) -> [PASS][47] +1 similar issue
> [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb4/igt@kms_psr@psr2_cursor_mmap_cpu.html
> [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
>
> * igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
> - shard-kbl: [INCOMPLETE][48] ([fdo#103665]) -> [PASS][49]
> [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-kbl3/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
> [49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-kbl6/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
>
> * igt@prime_busy@hang-bsd2:
> - shard-iclb: [SKIP][50] ([fdo#109276]) -> [PASS][51] +13 similar issues
> [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb5/igt@prime_busy@hang-bsd2.html
> [51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb2/igt@prime_busy@hang-bsd2.html
>
>
> #### Warnings ####
>
> * igt@gem_mocs_settings@mocs-isolation-bsd2:
> - shard-iclb: [SKIP][52] ([fdo#109276]) -> [FAIL][53] ([fdo#111330])
> [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb7/igt@gem_mocs_settings@mocs-isolation-bsd2.html
> [53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb4/igt@gem_mocs_settings@mocs-isolation-bsd2.html
>
> * igt@gem_mocs_settings@mocs-settings-bsd2:
> - shard-iclb: [FAIL][54] ([fdo#111330]) -> [SKIP][55] ([fdo#109276])
> [54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6982/shard-iclb2/igt@gem_mocs_settings@mocs-settings-bsd2.html
> [55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/shard-iclb8/igt@gem_mocs_settings@mocs-settings-bsd2.html
>
>
> {name}: This element is suppressed. This means it is ignored when computing
> the status of the difference (SUCCESS, WARNING, or FAILURE).
>
> [fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
> [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
> [fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540
> [fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
> [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
> [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
> [fdo#108686]: https://bugs.freedesktop.org/show_bug.cgi?id=108686
> [fdo#108767]: https://bugs.freedesktop.org/show_bug.cgi?id=108767
> [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
> [fdo#109385]: https://bugs.freedesktop.org/show_bug.cgi?id=109385
> [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
> [fdo#110548]: https://bugs.freedesktop.org/show_bug.cgi?id=110548
> [fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325
> [fdo#111329]: https://bugs.freedesktop.org/show_bug.cgi?id=111329
> [fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330
> [fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
>
>
> Participating hosts (16 -> 6)
> ------------------------------
>
> ERROR: It appears as if the changes made in IGTPW_3518_full prevented too many machines from booting.
>
> Missing (10): shard-skl pig-hsw-4770r shard-tglb1 shard-tglb2 shard-tglb3 shard-tglb4 shard-tglb5 shard-tglb6 pig-glk-j5005 pig-skl-6260u
>
>
> Build changes
> -------------
>
> * CI: CI-20190529 -> None
> * IGT: IGT_5208 -> IGTPW_3518
> * Piglit: piglit_4509 -> None
>
> CI-20190529: 20190529
> CI_DRM_6982: 328a82d454d71506a156d389da4cba24f9ae3a34 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGTPW_3518: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/index.html
> IGT_5208: c0131b4f132acf287d9d05b0f5078003d3159e1c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3518/index.html
> _______________________________________________
> 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
prev parent reply other threads:[~2019-10-02 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 11:32 [igt-dev] [PATCH i-g-t 0/2] Add a new IGT test to validate DC3CO state Jeevan B
2019-10-01 11:32 ` [igt-dev] [PATCH i-g-t 1/2] igt/i915/i915_pm_dc: DC3CO PSR2 helpers Jeevan B
2019-10-01 11:32 ` [igt-dev] [PATCH i-g-t 2/2] Add a new IGT test to validate DC3CO state Jeevan B
2019-10-02 16:10 ` [igt-dev] [PATCH i-g-t 2/2] Add a new IGT test to validate DC3CO statey Anshuman Gupta
2019-10-01 12:16 ` [igt-dev] ✓ Fi.CI.BAT: success for Add a new IGT test to validate DC3CO state. (rev3) Patchwork
2019-10-01 17:58 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-10-02 9:32 ` Anshuman Gupta [this message]
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=20191002093202.GA29793@intel.com \
--to=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@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.