[igt-dev] ✗ Fi.CI.IGT: failure for i915/gem_exec_basic: Use dynamic subtests

Petri Latvala petri.latvala at intel.com
Thu Jan 9 10:35:46 UTC 2020


On Wed, Jan 08, 2020 at 05:06:43PM +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: i915/gem_exec_basic: Use dynamic subtests
> URL   : https://patchwork.freedesktop.org/series/71733/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_7699_full -> IGTPW_3904_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with IGTPW_3904_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in IGTPW_3904_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_3904/index.html
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in IGTPW_3904_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt at gem_busy@close-race:
>     - shard-hsw:          NOTRUN -> [TIMEOUT][1]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3904/shard-hsw1/igt@gem_busy@close-race.html
> 
>   * igt at gem_eio@kms:
>     - shard-hsw:          [PASS][2] -> [DMESG-WARN][3]
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7699/shard-hsw2/igt@gem_eio@kms.html
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3904/shard-hsw5/igt@gem_eio@kms.html


Lakshmi, some false positives for you above.




> 
>   
> New tests
> ---------
> 
>   New tests have been introduced between CI_DRM_7699_full and IGTPW_3904_full:
> 
> ### New IGT tests (18) ###
> 
>   * igt at gem_exec_basic@basic:
>     - Statuses : 1 pass(s)
>     - Exec time: [0.00] s

I was wondering where the heck this came from (it's the base subtest,
and should not be reported) but the shard round this was in was
incomplete and the report generation was done with an older IGT.

Arek, wasn't updating the report-generating-IGT made automatic on
post-merge? It hasn't happened for this report.



-- 
Petri Latvala


More information about the igt-dev mailing list