To help make sure we are running tests in the ideal number of threads,
print load stats to make obvious when there's a problem with
utilization.
This will be specially useful when we run tests on a wider variety of
devices.
Signed-off-by: Tomeu Vizoso <tomeu.viz...@collabora.com>
---
src/gallium/drivers/panfrost/ci/lava-deqp.yml.jinja2 | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/drivers/panfrost/ci/lava-deqp.yml.jinja2
b/src/gallium/drivers/panfrost/ci/lava-deqp.yml.jinja2
index 56cbdf913f46..a04da3e182ec 100644
--- a/src/gallium/drivers/panfrost/ci/lava-deqp.yml.jinja2
+++ b/src/gallium/drivers/panfrost/ci/lava-deqp.yml.jinja2
@@ -53,6 +53,7 @@ actions:
- echo 3 > /proc/sys/kernel/printk
- echo performance >
/sys/devices/platform/ff9a0000.gpu/devfreq/devfreq0/governor
- sh /deqp/deqp-runner.sh
+ - cat /proc/loadavg
parse:
pattern: '(?P<test_case_id>\S*):\s+(?P<result>(pass|fail))'
from: inline
--
2.20.1
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
