[PATCH i-g-t] tests/intel/xe_fault_injection: Ignore enable activity stats error

Michal Wajdeczko michal.wajdeczko at intel.com
Wed May 28 21:53:55 UTC 2025



On 28.05.2025 15:30, Satyanarayana K V P wrote:
> Add some more GuC fault messages in the dmesg ignore list.
> 
> Signed-off-by: Satyanarayana K V P <satyanarayana.k.v.p at intel.com>
> ---
> Cc: Jonathan Cavitt <jonathan.cavitt at intel.com>
> Cc: John Harrison <John.C.Harrison at Intel.com>
> ---
>  tests/intel/xe_fault_injection.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tests/intel/xe_fault_injection.c b/tests/intel/xe_fault_injection.c
> index f9bd5c761..4ca8a34bf 100644
> --- a/tests/intel/xe_fault_injection.c
> +++ b/tests/intel/xe_fault_injection.c
> @@ -85,6 +85,7 @@ static void ignore_faults_in_dmesg(const char function_name[])
>  		strcat(regex, "|GT[0-9a-fA-F]*: Failed to initialize uC .-ENOMEM");
>  		strcat(regex, "|GT[0-9a-fA-F]*: Failed to enable GuC CT	.-ENOMEM");
>  		strcat(regex, "|GT[0-9a-fA-F]*: GuC PC query task state failed:	-ENOMEM");
> +		strcat(regex, "|GT[0-9a-fA-F]*: failed to enable activity stats-[0-9]*");

are we really going to add more and more specific error messages to the
IGT filter just to make CI happy? note that this could be never ending
story and still very fragile to any changes on the driver side in
functions or component reordering or improvements in messages or driver
attempts to recover from non-fatal errors

can't we just ignore *ALL* error messages during fault injection tests?

after all, as we are injecting errors, our only expectation should be
that driver will not crash or hit asserts, regardless how many error
messages will be printed in the meantime, as we don't expect error free
run here and we can't expect specific error message either

>  	}
>  
>  	igt_emit_ignore_dmesg_regex(regex);



More information about the igt-dev mailing list