1. 08 Nov, 2018 1 commit
  2. 18 Oct, 2017 1 commit
  3. 17 Apr, 2016 1 commit
  4. 08 Feb, 2016 3 commits
  5. 11 Nov, 2015 1 commit
  6. 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>
  7. 02 Sep, 2015 1 commit
  8. 15 Jul, 2015 1 commit
    • Dylan Baker's avatar
      compression.py: fix compression to be updated when piglit.conf is reloaded · 0086660c
      Dylan Baker authored
      There is currently a bug in piglit (demonstrated by the previous patch),
      that shows that compression is hard set before piglit.conf is loaded in
      run, and not affected by any subsequent re-reads of piglit.conf. This is
      problematic, resulting in the compression mode being either
      PIGLIT_COMPRESSION or the default value, bz2.
      This patch corrects that by removing constant values and replacing them
      with a getting function.
      Signed-off-by: default avatarDylan Baker <dylanx.c.baker@intel.com>
  9. 09 Jul, 2015 1 commit
    • Dylan Baker's avatar
      framework: Add ability to set a compression method on file backends · 7be0c99c
      Dylan Baker authored
      This creates a framework for compressing results as part of the
      FileBackend class. This allows for the simple addition of compression
      formats (gz is easily possible in python2, xz in python3), but does not
      actually implement any compression. zip and bz2 compression are also
      possible, although they'll require a little more code.
      This patch implements a framework, and tests for that framework.
      The goal is that other compression methods can easily be added to piglit
      simply by setting a few values in framework/backends/compression, and
      then everything will just work.
      This will allow junit results that are compressed to be read, but
      doesn't add support to junit for compressing results, since junit is
      mainly intended for consumption by jenkins, which doesn't understand
      v2: - replace tests decorator set_compression with use of
            utils.set_piglit_conf. This is better because it uses a generic
            tools, and because set_compression is somewhat misleading of a
      v3: - backport changes from my attempt to port this to python3. There
            are significant differences between python2 and python3 compression
            handling because of the bytes/str/unicode differences between the
            two versions. There are also code cleanups from that work here
          - Make a better effort to protect the unit tests from the
            environment around them. The goal is that the tests control the
            compression options 100%, with no chance of piglit.conf or
            environment variables affecting the tests.
          - reduce code duplication in unit tests
          - add additional unit tests as made possible by refactoring changes
      v4: - add additional unit tests
      Signed-off-by: default avatarDylan Baker <dylanx.c.baker@intel.com>
  10. 07 Jul, 2015 1 commit
  11. 05 May, 2015 1 commit
    • Dylan Baker's avatar
      framework: write an incomplete status before running tests · 8ce57882
      Dylan Baker authored
      This sets the file based backends (both the json and junit) to write out
      an incomplete status before starting the test. (for junit this is a
      'fail' with a message of 'incomplete', junit is a fairly limited
      format). When the test is completed this incomplete status is
      overwritten with the final status.
      This patch also adds a new mode to the 'summary console' option, '-i',
      which will list all tests with an incomplete status.
      This will allow a developer to see what tests failed when a system
      crashed, or what tests were running when they aborted piglit.
      Signed-off-by: default avatarDylan Baker <dylanx.c.baker@intel.com>
      Reviewed-by: Mark Janes's avatarMark Janes <mark.a.janes@intel.com>
  12. 24 Dec, 2014 1 commit
    • Dylan Baker's avatar
      framework: Cleanup imports · 2d34c2d5
      Dylan Baker authored
      Makes 2 changes, all of which should have absolutely zero effect
      1) breaks the imports into three newline separated groups: builtins,
      installed modules, local modules
      2) use print_function and absolute_import in all modules.
      Signed-off-by: default avatarDylan Baker <dylanx.c.baker@intel.com>
  13. 02 Oct, 2014 5 commits