1. 11 Oct, 2013 1 commit
  2. 23 Sep, 2013 2 commits
  3. 17 Sep, 2013 1 commit
  4. 28 Aug, 2013 1 commit
  5. 29 Jul, 2013 1 commit
  6. 16 May, 2013 1 commit
  7. 13 May, 2013 1 commit
    • Dylan Baker's avatar
      python: Convert tabs to spaces · b9c4f967
      Dylan Baker authored
      PEP 8 specifies that all indents should be either 4 spaces or an
      equivalent tab indent, but without mixing tabs and spaces, with a
      preference for spaces over tabs because they are absolute. Tabs and
      spaces should not be mixed because they lead to expected indent level
      Currently piglit uses a mixture of spaces and tabs, this patch uses the
      python tools reindent.py to convert the tabs to spaces.
      Signed-off-by: Dylan Baker's avatarDylan Baker <baker.dylan.c@gmail.com>
      v2: Rebase against master, fix apparent unintentional unindentation of
          help text in piglit-summary.py (changes by anholt)
      Reviewed-by: Eric Anholt's avatarEric Anholt <eric@anholt.net>
  8. 10 Mar, 2013 5 commits
  9. 08 Feb, 2013 1 commit
  10. 03 Jan, 2013 1 commit
    • Kenneth Graunke (semi-AFK still)'s avatar
      glean: Remove support for writing results databases. · 9a4bc09d
      Kenneth Graunke (semi-AFK still) authored
      At this point, Glean wasn't writing anything interesting anyway;
      it was just clutter.
      Since there's no need to specify a results directory on the command line
      any longer, this patch also removes the -r option, making "run tests"
      the default action.
      This also allows us to simplify the Piglit runner framework a little:
      it no longer has to pass around the results directory just to pass to
  11. 20 Oct, 2012 1 commit
  12. 16 Jul, 2012 1 commit
  13. 12 Mar, 2012 1 commit
    • Kenneth Graunke (semi-AFK still)'s avatar
      Make valgrind testing a command line option rather than extra tests. · fefa962e
      Kenneth Graunke (semi-AFK still) authored
      Valgrind testing is useful, but really should be done as a separate
      exercise from the usual regression testing, as it takes way too long.
      Rather than including it by default in all.tests and making people
      exclude it with the -x valgrind option (or by using quick.tests), it
      makes sense to explicitly request valgrind testing with --valgrind.
      To perform valgrind testing:
      $ piglit-run.py --valgrind <options> tests/quick.tests results/vg-1
      The ExecTest class now handles Valgrind wrapping natively, rather than
      relying on the tests/valgrind-test/valgrind-test shell script wrapper.
      This provides a huge benefit: we can leverage the interpretResult()
      function to make it work properly for any subclass of ExecTest.  The
      old shell script only worked for PlainExecTest (piglit) and GleanTest.
      Another small benefit is that you can now use --valgrind with any test
      profile (such as quick.tests).  Also, you can use all.tests without
      having to remember to specify "-x valgrind".
      Signed-off-by: Kenneth Graunke (semi-AFK still)'s avatarKenneth Graunke <kenneth@whitecape.org>
  14. 02 Mar, 2012 2 commits
    • Kenneth Graunke (semi-AFK still)'s avatar
      Add the ability to resume an interrupted test run where it left off. · e627eb88
      Kenneth Graunke (semi-AFK still) authored
      GPUs like to hang, especially when barraged with lots of mean Piglit
      tests.  Usually this results in the poor developer having to figure out
      what test hung, blacklist it via -x, and start the whole test run over.
      This can waste a huge amount of time, especially when many tests hang.
      This patch adds the ability to resume a Piglit run where you left off.
      The workflow is:
      $ piglit-run.py -t foo tests/quick.tests results/foobar-1
      <interrupt the test run somehow>
      $ piglit-run.py -r -x bad-test results/foobar-1
      To accomplish this, piglit-run.py now stores the test profile
      (quick.tests) and -t/-x options in the JSON results file so it can tell
      what you were originally running.  When run with the --resume option, it
      re-reads the results file to obtain this information (repairing broken
      JSON if necessary), rewrites the existing results, and runs any
      remaining tests.
      Results files produced after this commit are incompatible with older
      piglit-summary-html.py (due to the extra "option" section.)
      Signed-off-by: Kenneth Graunke (semi-AFK still)'s avatarKenneth Graunke <kenneth@whitecape.org>
      Reviewed-by: Paul Berry's avatarPaul Berry <stereotype441@gmail.com>
    • Kenneth Graunke (semi-AFK still)'s avatar
      Move writing of JSON 'tests' dictionary section out of TestProfile.run. · 506ab469
      Kenneth Graunke (semi-AFK still) authored
      When resuming an interrupted piglit run, we'll want to output both
      existing and new results into the same 'tests' section.  Since
      TestProfile.run only handles newly run tests, it can't open/close the
      JSON dictionary.
      So, move it to the caller in piglit-run.py.
      Signed-off-by: Kenneth Graunke (semi-AFK still)'s avatarKenneth Graunke <kenneth@whitecape.org>
      Reviewed-by: Paul Berry's avatarPaul Berry <stereotype441@gmail.com>
  15. 24 Feb, 2012 1 commit
  16. 17 Jan, 2012 1 commit
  17. 13 Oct, 2011 1 commit
    • Matěj Cepl's avatar
      Make Python scripts independent of the current working directory · 88ecb306
      Matěj Cepl authored
      The main purpose of this patch is to make piglit independent of the
      current working directory, so it is possible to package piglit as a RPM
      package (with binaries symlinked to /usr/bin, most of the files in
      read-only /usr/lib*/piglit directory, and results somewhere else).
      So it is now possible to run
      $ piglit-run tests/quick-driver.tests /tmp/piglit
      and then with this command
      $ piglit-summary-html --overwrite /tmp/piglit/results /tmp/piglit/main
      generate a report in /tmp/piglit/results/index.html & al.
      Signed-off-by: default avatarMatěj Cepl <mcepl@redhat.com>
      Reviewed-by: Paul Berry's avatarPaul Berry <stereotype441@gmail.com>
  18. 05 Aug, 2011 1 commit
  19. 30 Jul, 2011 2 commits
  20. 14 Jul, 2011 1 commit
    • chadversary's avatar
      framework: Replace custom serialization format with json · b2ae931c
      chadversary authored
      The results file produced by piglit-run.py contains a serialized
      TestrunResult, and the serialization format was horridly homebrew. This
      commit replaces that insanity with json.
          - Net loss of 113 lines of code (ignoring comments and empty lines).
          - By using the json module in the Python standard library, serializing
            and unserializing is nearly as simple as `json.dump(object, file)`
            and `json.load(object, file)`.
          - By using a format that is easy to manipulate, it is now simple to
            extend Piglit to allow users to embed custom data into the results
      As a side effect, the summary file is no longer needed, so it is no longer
      Reviewed-by: Paul Berry's avatarPaul Berry <stereotype441@gmail.com>
      Signed-off-by: chadversary's avatarChad Versace <chad@chad-versace.us>
  21. 10 Feb, 2011 1 commit
  22. 29 Jul, 2010 1 commit
  23. 23 Aug, 2009 1 commit
  24. 22 Aug, 2009 1 commit
  25. 12 Jun, 2008 1 commit
    • Nicolai Hähnle's avatar
      Generate abbreviated results · eb6359d4
      Nicolai Hähnle authored
      The results files can get rather huge when tests fail, because tests like
      glean/blendFunc output a lot of debugging data, which we all record.
      Now, we generate an additional .../summary file, in which the info string
      is simply truncated. Pretty stupid, but it should give enough info to get
      an idea of the rough kind of failure.
      Add a new option for piglit-summary-html.py, to choose between full or
      abbreviated info when both are present.
  26. 06 Jun, 2008 1 commit
  27. 21 Feb, 2008 1 commit
  28. 03 Apr, 2007 1 commit
  29. 25 Mar, 2007 4 commits