On Mon, Dec 23, 2024 at 08:18:46PM +0100, Andi Shyti wrote: > Hi Sebastian, > > On Fri, Dec 20, 2024 at 02:17:14PM +0100, Andi Shyti wrote: > > From: Sebastian Brzezinka <[email protected]> > > > > TAINT_WARN is used to notify CI about non-recoverable failures, which > > require device to be restarted. In some cases, there is no sufficient > > information about the reason for the restart. The test runner is just > > killed, and DUT is rebooted, logging only 'probe with driver i915 failed > > with error -4' to dmesg. > > > > Printing error to dmesg before TAINT_WARN, would explain why the device > > has been restarted, and what caused the malfunction in the first place. > > > > Signed-off-by: Sebastian Brzezinka <[email protected]> > > Reviewed-by: Andi Shyti <[email protected]> > > Signed-off-by: Andi Shyti <[email protected]> > > it's hard to receive green lights from CI. Anyway, I merged it to > drm-intel-gt-next since all the failures look completely > unrelated.
Side note: You can trigger a re-run from patchwork without resend. Raag
