Sometimes the Piglit start-up time dominates the total runtime.
Including this in the time_elapsed attribute is more informative.
---
framework/programs/run.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/framework/programs/run.py b/framework/programs/run.py
index 5fe8419..14fb764 100644
--- a/framework/programs/run.py
+++ b/framework/programs/run.py
@@ -327,6 +327,8 @@ def run(input_):
stripped = (t.split('#')[0].strip() for t in test_list)
forced_test_list = [t for t in stripped if t]
+ time_elapsed = TimeAttribute(start=time.time())
+
backend = backends.get_backend(args.backend)(
args.results_path,
junit_suffix=args.junit_suffix,
@@ -362,8 +364,6 @@ def run(input_):
if args.include_tests:
p.filters.append(profile.RegexFilter(args.include_tests))
- time_elapsed = TimeAttribute(start=time.time())
-
profile.run(profiles, args.log_level, backend, args.concurrency)
time_elapsed.end = time.time()
--
1.9.1
_______________________________________________
Piglit mailing list
Piglit@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/piglit
