Re: ✗ Fi.CI.IGT: failure for tests/intel/gem_exec_capture: Check for partial register captures (rev2)

John Harrison john.c.harrison at intel.com
Tue Mar 5 18:07:21 UTC 2024


On 3/5/2024 09:50, Kamil Konieczny wrote:
> Hi igt-dev,
> On 2024-03-01 at 23:08:10 -0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: tests/intel/gem_exec_capture: Check for partial register captures (rev2)
>> URL   : https://patchwork.freedesktop.org/series/130332/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from CI_DRM_14370_full -> IGTPW_10760_full
>> ====================================================
>>
>> Summary
>> -------
>>
>>    **FAILURE**
>>
>>    Serious unknown changes coming with IGTPW_10760_full absolutely need to be
>>    verified manually.
>>    
>>    If you think the reported changes have nothing to do with the changes
>>    introduced in IGTPW_10760_full, please notify your bug team (I915-ci-infra at lists.freedesktop.org) 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_10760/index.html
>>
>> Participating hosts (8 -> 8)
>> ------------------------------
>>
>>    No changes in participating hosts
>>
>> Possible new issues
>> -------------------
>>
>>    Here are the unknown changes that may have been introduced in IGTPW_10760_full:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>>    * igt at gem_exec_capture@capture at ccs3-smem:
>>      - shard-dg2:          [PASS][1] -> [FAIL][2] +13 other tests fail
>>     [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14370/shard-dg2-10/igt@gem_exec_capture@capture@ccs3-smem.html
>>     [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10760/shard-dg2-6/igt@gem_exec_capture@capture@ccs3-smem.html
>>
>>    * igt at gem_exec_capture@capture at rcs0-smem:
>>      - shard-mtlp:         [PASS][3] -> [FAIL][4] +3 other tests fail
>>     [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14370/shard-mtlp-8/igt@gem_exec_capture@capture@rcs0-smem.html
>>     [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10760/shard-mtlp-6/igt@gem_exec_capture@capture@rcs0-smem.html
>>
>>    * igt at gem_exec_capture@capture at vecs0-lmem0:
>>      - shard-dg1:          [PASS][5] -> [FAIL][6] +3 other tests fail
>>     [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14370/shard-dg1-13/igt@gem_exec_capture@capture@vecs0-lmem0.html
>>     [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10760/shard-dg1-19/igt@gem_exec_capture@capture@vecs0-lmem0.html
>>
>>    * igt at gem_exec_capture@userptr:
>>      - shard-dg1:          NOTRUN -> [FAIL][7]
>>     [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10760/shard-dg1-18/igt@gem_exec_capture@userptr.html
>>
> Above are bugs which were spotted by a change in test.
Correct, this is the test saying that the kernel is broken.

How does one know what build of the kernel the test was run against? 
Specifically, does it contain this patch:
e45afbeb59347 drm/i915/guc: Correct capture of EIR register on hang

If not, then the test is expected to fail.

John.


>
>>    * igt at i915_pm_rpm@gem-execbuf-stress at extra-wait-lmem0:
>>      - shard-dg1:          [PASS][8] -> [ABORT][9] +1 other test abort
>>     [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14370/shard-dg1-15/igt@i915_pm_rpm@gem-execbuf-stress@extra-wait-lmem0.html
>>     [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10760/shard-dg1-16/igt@i915_pm_rpm@gem-execbuf-stress@extra-wait-lmem0.html
>>
>>    * igt at i915_pm_rpm@gem-execbuf-stress at lmem0:
>>      - shard-dg2:          [PASS][10] -> [ABORT][11] +1 other test abort
>>     [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14370/shard-dg2-7/igt@i915_pm_rpm@gem-execbuf-stress@lmem0.html
>>     [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10760/shard-dg2-11/igt@i915_pm_rpm@gem-execbuf-stress@lmem0.html
>>
>>    * igt at vgem_basic@unload:
>>      - shard-glk:          [PASS][12] -> [INCOMPLETE][13]
>>     [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14370/shard-glk8/igt@vgem_basic@unload.html
>>     [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10760/shard-glk7/igt@vgem_basic@unload.html
>>
> These are unrelated.
>
> Regards,
> Kamil
>
>>    
>> New tests
>> ---------
>>
>>    New tests have been introduced between CI_DRM_14370_full and IGTPW_10760_full:
>>
>> ### New IGT tests (4) ###
>>
>>    * igt at kms_cursor_edge_walk@128x128-top-bottom at pipe-a-dp-4:
>>      - Statuses : 1 pass(s)
>>      - Exec time: [3.52] s
>>
>>    * igt at kms_cursor_edge_walk@128x128-top-bottom at pipe-d-dp-4:
>>      - Statuses : 1 pass(s)
>>      - Exec time: [3.31] s
>>
>>    * igt at kms_cursor_edge_walk@256x256-right-edge at pipe-a-dp-4:
>>      - Statuses : 1 pass(s)
>>      - Exec time: [3.46] s
>>
>>    * igt at kms_cursor_edge_walk@256x256-right-edge at pipe-d-dp-4:
>>      - Statuses : 1 pass(s)
>>      - Exec time: [3.31] s
>>
>>    
>>
>> Known issues
>> ------------
>>
>>    Here are the changes found in IGTPW_10760_full that come from known issues:
>>
>> ### IGT changes ###
>>
>> #### Issues hit ####
>>
> ...cut...
>
>> == Logs ==
>>
>> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_10760/index.html



More information about the igt-dev mailing list