Re: ✗ Fi.CI.BAT: failure for Subject: [PATCH dii-client v6 0/4] drm/i915: Define and use GuC and CTB TLB invalidation routines

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

 



Hi Jonathan,

> CI changes
> 
> Possible regressions
> 
>   • boot:
>       □ bat-dg1-5: PASS -> FAIL
> 
> IGT changes
> 
> Possible regressions
> 
>   • igt@kms_addfb_basic@addfb25-framebuffer-vs-set-tiling:
> 
>       □ bat-adlm-1: PASS -> INCOMPLETE
>   • igt@kms_busy@basic@flip:
> 
>       □ bat-adlp-11: PASS -> ABORT
> 
>       □ bat-adlp-6: PASS -> INCOMPLETE
> 
>   • igt@kms_busy@basic@modeset:
> 
>       □ bat-adlp-11: PASS -> DMESG-WARN
>   • igt@kms_force_connector_basic@force-connector-state:
> 
>       □ bat-rpls-1: PASS -> INCOMPLETE

Although these failures appear very consistently, they don't look
related to your patch. But still I wonder why they show up so
consistently.

Is anyone from the list able to provide some thoughts?

Andi



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

  Powered by Linux