[Piglit] [PATCH] cl: Add tests for some cases that were broken with function calls
jan.vesely at rutgers.edu
Mon Jun 3 16:46:18 UTC 2019
On Mon, 2019-06-03 at 10:31 -0400, Matt Arsenault wrote:
> > On Jun 2, 2019, at 2:36 PM, Jan Vesely <jan.vesely at rutgers.edu> wrote:
> > he other problem is that even with killed process hung GPU usually
> > makes the machine unable to suspend or reboot on its own, which kills
> > remote testing.
> > I'd need to recheck if that's still the case with linux-5.1.
> I was able to interrupt the process normally and everything worked
> OK with rocm (which due to the device name regex, its the only
> platform this runs) without my fix applied.
Does rocm do anything special other than using compute rings?
What was the HW you tested?
I checked that raven can reboot after gpu hangs/crashes (not suspend,
but that's probably one of many raven problems). I'd like to check
carrizo/iceland too, as that's the machine that get accessed remotely.
Other than that I think it's OK to just put default 30s timeout on all
CL tests, even debug build of LLVM shouldn't need more than that.
> Piglit mailing list
> Piglit at lists.freedesktop.org
Jan Vesely <jan.vesely at rutgers.edu>
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: This is a digitally signed message part
More information about the Piglit