[igt-dev] ✗ Fi.CI.IGT: failure for lib: Force rescan when module is loaded

[Vudum, Lakshminarayana]

At the moment we are tracking such failures on TGL here https://gitlab.freedesktop.org/drm/intel/-/issues/5361

Re-reported.

Lakshmi.

-----Original Message-----
From: De Marchi, Lucas <lucas.demarchi at intel.com> 
Sent: Monday, July 25, 2022 3:31 AM
To: igt-dev at lists.freedesktop.org
Cc: Vudum, Lakshminarayana <lakshminarayana.vudum at intel.com>
Subject: Re: ✗ Fi.CI.IGT: failure for lib: Force rescan when module is loaded

On Sat, Jul 23, 2022 at 08:57:29PM +0000, Patchwork wrote:
>== Series Details ==
>
>Series: lib: Force rescan when module is loaded
>URL   : https://patchwork.freedesktop.org/series/106635/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from IGT_6595_full -> IGTPW_7554_full 
>====================================================
>
>Summary
>-------
>
>  **FAILURE**
>
>  Serious unknown changes coming with IGTPW_7554_full absolutely need 
> to be  verified manually.
>
>  If you think the reported changes have nothing to do with the changes  
> introduced in IGTPW_7554_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_7554/index.html
>
>Participating hosts (9 -> 10)
>------------------------------
>
>  Additional (1): shard-dg1
>
>Possible new issues
>-------------------
>
>  Here are the unknown changes that may have been introduced in IGTPW_7554_full:
>
>### IGT changes ###
>
>#### Possible regressions ####
>
>  * igt at api_intel_allocator@fork-simple-stress-signal:
>    - shard-tglb:         [PASS][1] -> [INCOMPLETE][2]
>   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6595/shard-tglb5/igt@api_intel_allocator@fork-simple-stress-signal.html
>   [2]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7554/shard-tglb1/igt@ap
> i_intel_allocator at fork-simple-stress-signal.html

 From https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_7554/shard-tglb1/dmesg0.txt
it looks like machine crashed while starting the test and shouldn't be caused by this patch that simply updates the cached list of devices in userspace.

Lucas De Marchi