Re: ✗ Fi.CI.IGT: failure for Update bxt_sanitize_cdclk() for Xe2_LPD (rev3)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Gustavo Sousa (2024-01-08 14:27:46-03:00)
>Quoting Gustavo Sousa (2024-01-08 10:35:56-03:00)
>>Quoting Patchwork (2024-01-05 21:14:37-03:00)
>>>== Series Details ==
>>>
>>>Series: Update bxt_sanitize_cdclk() for Xe2_LPD (rev3)
>>>URL   : https://patchwork.freedesktop.org/series/128175/
>>>State : failure
>>>
>>>== Summary ==
>>>
>>>CI Bug Log - changes from CI_DRM_14080_full -> Patchwork_128175v3_full
>>>====================================================
>>>
>>>Summary
>>>-------
>>>
>>>  **FAILURE**
>>>
>>>  Serious unknown changes coming with Patchwork_128175v3_full absolutely need to be
>>>  verified manually.
>>>  
>>>  If you think the reported changes have nothing to do with the changes
>>>  introduced in Patchwork_128175v3_full, please notify your bug team (I915-ci-infra@xxxxxxxxxxxxxxxxxxxxx) to allow them
>>>  to document this new failure mode, which will reduce false positives in CI.
>>>
>>>  
>>>
>>>Participating hosts (8 -> 8)
>>>------------------------------
>>>
>>>  No changes in participating hosts
>>>
>>>Possible new issues
>>>-------------------
>>>
>>>  Here are the unknown changes that may have been introduced in Patchwork_128175v3_full:
>>>
>>>### IGT changes ###
>>>
>>>#### Possible regressions ####
>>>
>>>  * igt@kms_vblank@query-busy-hang@pipe-c-hdmi-a-2:
>>>    - shard-glk:          [PASS][1] -> [INCOMPLETE][2]
>>>   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14080/shard-glk6/igt@kms_vblank@query-busy-hang@xxxxxxxxxxxxxxxxxxxx
>>>   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_128175v3/shard-glk7/igt@kms_vblank@query-busy-hang@xxxxxxxxxxxxxxxxxxxx
>>
>>The dmesg output do not provide conclusive data for the INCOMPLETE status and I
>>believe the issue is unrelated, since the real functional change is on the
>>driver initialization path.
>>
>>However, for sanity sake, as GLK takes the bxt_sanitize_cdclk() path during
>>initialization, could we re-report, please?
>
>Re-sending this now as a member of I915-ci-infra@xxxxxxxxxxxxxxxxxxxxx; my
>previous email went into a moderation queue because I was not a member.

One last try, as it now complains that the message is too big...

--
Gustavo Sousa




[Index of Archives]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux