1. 12 Jan, 2016 1 commit
  2. 08 Oct, 2015 1 commit
  3. 22 Sep, 2015 1 commit
    • Dylan Baker's avatar
      framework: replace TestResult dict with an object · b365367f
      Dylan Baker authored
      This is a very invasive patch, because it replaces one of our core
      data-structures with a completely different kind of object. This new
      object is not a dict-like object (it doesn't use obj[key] = value
      syntax), instead it's a standard object with the standard object
      attributes. So result['time'] becomes result.time.
      This approach has a couple of advantages. First, it allows us to use
      properties, which allows us to encapsulate a lot of distributed logic
      from the summary module in the results module, and in a way that is
      easier to test for correctness. The second advantage of that
      encapsulation is that correct behavior is used everywhere, instead of
      just in most places. Finally, it allows us to use the flyweight pattern
      on the results objects, limiting the amount of memory consumed.
      Signed-off-by: default avatarDylan Baker <dylanx.c.baker@intel.com>
  4. 03 Sep, 2014 1 commit
  5. 24 Apr, 2014 1 commit
    • Dylan Baker's avatar
      tests/xts.py: Add a tests file for the X Test suite. · e1057c4a
      Dylan Baker authored
      This adds support for running XTS from piglit.
      This patch was original written by Eric Anholt, but I've cleaned it up
      and reworked parts of it for upstreaming, and as a result I've attached
      my name as the author so ``git bisect'' and ``git blame'' will send
      angry mail my way instead of Eric's.
      v2: - Don't break dmesg reporting
          - Use str.format consistently
          - populate profile after check for xtest symlink
      v3: - rebase against master
          - fix spelling errors
      Signed-off-by: Dylan Baker's avatarDylan Baker <baker.dylan.c@gmail.com>
      Reviewed-by: Eric Anholt's avatarEric Anholt <eric@anholt.net>
  6. 18 Apr, 2014 2 commits
  7. 05 Nov, 2013 1 commit
  8. 24 Oct, 2013 1 commit
  9. 23 Sep, 2013 1 commit
    • Marek Olšák's avatar
      Optionally capture dmesg changes for each test and report them in a summary · e85194b1
      Marek Olšák authored
      The Radeon driver writes GPU page faults to dmesg and we need to know which
      tests caused them.
      If there is any change in dmesg during a test run, the test result is changed
      as follows:
      * pass -> dmesg-warn
      * warn -> dmesg-warn
      * fail -> dmesg-fail
      Dmesg is captured before and after each test and the difference between the two
      is stored in the test summary.
      The piglit-run.py parameter which enables this behavior is --dmesg. It's also
      recommended to use -c0.
      v2: - address some of Dylan's remarks, mainly bug fixes
          - fix get_dmesg_diff
      Reviewed-by: Dylan Baker's avatarDylan Baken <baker.dylan.c@gmail.com>
  10. 15 Aug, 2013 1 commit
  11. 31 May, 2013 3 commits