summaryrefslogtreecommitdiff
path: root/XorgTesting.mdwn
diff options
context:
space:
mode:
authordbaker <dbaker@web>2016-02-09 19:53:43 +0100
committerxorg <iki-xorg@freedesktop.org>2016-02-09 19:53:43 +0100
commit6b1be2224eb1f72bb201d6f59136c916681cf113 (patch)
tree220ce1b2b9f03b7ddb53569448438d7c442aa886 /XorgTesting.mdwn
parent88955717069bc63277a7d42563c4e639ac8eeb48 (diff)
Update XTS instructions to use piglit.conf (linking into bin was incorrect)
Diffstat (limited to 'XorgTesting.mdwn')
-rw-r--r--XorgTesting.mdwn8
1 files changed, 5 insertions, 3 deletions
diff --git a/XorgTesting.mdwn b/XorgTesting.mdwn
index a3ca72eb..74fdf4fd 100644
--- a/XorgTesting.mdwn
+++ b/XorgTesting.mdwn
@@ -28,8 +28,10 @@ Note that these images don't necessarily represent what was *actually* rendered,
# git clone git://anongit.freedesktop.org/git/piglit.git
# cd piglit
- # mkdir bin
- # ln -s ~/my/path/to/xts bin/xtest
+ # cp piglit.conf.example piglit.conf
+ # $EDITOR piglit.conf
+
+And set [xts] path=~/source/xts (or wherever you download the xts repository)
Now, here's an example of using this to do some tests comparing two rendering modes in Xephyr. Xlib9 is the set of core rendering tests (not counting the window movement code, which also does rendering and is covered in another chapter).
@@ -38,7 +40,7 @@ Now, here's an example of using this to do some tests comparing two rendering mo
# killall Xephyr
# Xephyr :5 -noreset -ac -screen 1024x768 -glamor &
# DISPLAY=:5 ./piglit-run.py -t Xlib9 tests/xts.py results/xts-glamor
- # ./piglit-summary-html.py summary/mysum results/xts results/xts-glamor
+ # ./piglit summary html summary/mysum results/xts results/xts-glamor
# firefox summary/mysum/index.html
Take a look at changes.html for a common way of looking at piglit results as a developer (I don't care if things are still broken, I want to know if I broke or fixed new things).