[Mesa-dev] [shader-db 3/3] README: Make initial smoke tests steps internally consistent
Rhys Kidd
rhyskidd at gmail.com
Tue Jul 25 03:42:38 UTC 2017
No other stage of the suggested initial sanity.py test or other
tests uses a folder structure with *.results.
Use a consistent naming approach throughout the initial README to
make initial setup clearer.
Signed-off-by: Rhys Kidd <rhyskidd at gmail.com>
---
README | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README b/README
index 56ea52b62..c6961cfac 100644
--- a/README
+++ b/README
@@ -261,12 +261,12 @@ See also section 4.
To create some nice formatted test summaries, run
- $ ./piglit summary html summary/sanity results/sanity.results
+ $ ./piglit summary html summary/sanity results/sanity
Hint: You can combine multiple test results into a single summary.
During development, you can use this to watch for regressions:
- $ ./piglit summary html summary/compare results/baseline.results results/current.results
+ $ ./piglit summary html summary/compare results/baseline results/current
You can combine as many testruns as you want this way (in theory;
the HTML layout becomes awkward when the number of testruns increases)
--
2.11.0
More information about the mesa-dev
mailing list