Since commit "tests: use meta profiles"
(400dcd5cf18ac51ab8e9681d8ecab4132986efbd) some test sets are not
represented anymore as python scripts. So first, it would be good to
mention it, and second it would be good to mention that it would be
better to run the test sets using the set name, not dire
vkrunner recently added a new option (--device-id=) for selecting
the physical device. This is quite useful in a multi-GPU scenario.
This allows to set some vkrunner options via vkrunner:extra_args
in the configuration file or with PIGLIT_VKRUNNER_EXTRA_ARGS.
Signed-off-by: Samuel Pitoiset
---
> On Jun 3, 2019, at 12:46 PM, Jan Vesely wrote:
>
> Does rocm do anything special other than using compute rings?
> What was the HW you tested?
I don’t think so. This is on gfx900
> I checked that raven can reboot after gpu hangs/crashes (not suspend,
> but that's probably one of many raven
On Wed, 2019-06-05 at 17:48 -0400, Matt Arsenault wrote:
> > On Jun 3, 2019, at 12:46 PM, Jan Vesely wrote:
> >
> > Does rocm do anything special other than using compute rings?
> > What was the HW you tested?
> I don’t think so. This is on gfx900
>
>
> > I checked that raven can reboot after g
From: Jan Vesely
Signed-off-by: Jan Vesely
---
framework/test/piglit_test.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/framework/test/piglit_test.py b/framework/test/piglit_test.py
index 166c2f792ca..b4e6eb444e0 100644
--- a/framework/test/piglit_test.py
+++ b/framework/test/piglit_te