1. 01 Jun, 2015 1 commit
  2. 26 Jan, 2015 1 commit
    • Wang Shuo's avatar
      deqp: (V5)Add option to run subset of external dEQP-GLES3 · 656b41d4
      Wang Shuo authored
      Google have already added a subset of dEQP into Android CTS test,
      and we believe this part of dEQP have higher priority than the rest
      of dEQP test cases.
      The case list is stored at some xml files. Such as:
      It's git repo lives in the Android tree at
      [https://android.googlesource.com/platform/external/ \
      This patch is based on Chad's patch(Add test profile for external
      dEQP-GLES3 tests), and add an option to run the subset of dEQP-GLES3.
      The only differnce for the running method is: you need to set the
      environment variable PIGLIT_DEQP_MUSTPASS or the piglit.conf
      option deqp-gles3.mustpasslist,then it will run the subset of dEQP
      follow the test case list. If not set, it will still run the whole
      Tested on Intel HSW. There are 45866 test cases for the whole dEQP
      and 37354 test cases for the subset of dEQP using Android CTS test
      case list.
      1.Update the link of get test case list file.
      2.Using xml.etree.cElementTree module instead of re module.
      3.Fix some Piglit style issue
      1.Update the output issue.
      2.Fix some Piglit style issue.
      1.Fix some Piglit style issue.
      1.Fix some Piglit style issue.
      v6 (Dylan):
      - Remove trailing whitespace
      Signed-off-by: default avatarWang Shuo <shuo.wang@intel.com>
      Reviewed-by: default avatarDylan Baker <dylanx.c.baker@intel.com>
  3. 22 Dec, 2014 1 commit
    • Chad Versace's avatar
      deqp: Add test profile for external dEQP-GLES3 tests (v4) · 2f122df3
      Chad Versace authored
      Google opensourced the drawElements Quality Product Testsuite (dEQP) as
      part of the Android Lollipop release. It's git repo lives in the Android
      tree at [https://android.googlesource.com/platform/external/deqp/].
      This patch adds a new module, deqp_gles3.py, that runs the dEQP-GLES3
      tests.  It queries the 'deqp-gles3' executable at runtime for the list
      of testcases.  The module attempts queries the 'deqp-gles3' executable
      only if the environment variable PIGLIT_DEQP_GLES3_EXE or the
      piglit.conf option deqp-gles3.exe is set.
      Why do we need to use Pigit as the testrunner for dEQP? (After all, dEQP has
      its own testrunner). Because dEQP runs all tests in a single process. If test
      17530 of 55409 crashes, then the dEQP testrunner crashes and the remaining
      tests never run. Piglit doesn't suffer from that problem, because it runs each
      test as a separate process.
      Tested on Intel Ivybridge by running the command
          piglit run -t dEQP-GLES3/info/vendor \
            tests/deqp_gles3.py tests/quick.py results
      with and without PIGLIT_DEQP_GLES3_EXE set and with and without
      piglit.conf:deqp-gles.exe set. Also tested with various combinations of
      valid and invalid values for PIGLIT_DEQP_GLES_EXTRA_ARGS and
      Reviewed-by: Dylan Baker <dylanx.c.baker@intel.com> (v2)
      Reviewed-by: Michael W Mason <michael.w.mason@intel.com> (v4)
      Signed-off-by: default avatarChad Versace <chad.versace@linux.intel.com>
  4. 25 Sep, 2014 1 commit
    • Mark Janes's avatar
      Filter expected failures from JUnit output · 1921e13d
      Mark Janes authored
      Piglit test results are difficult to analyze with simpler JUnit
      visualizers like those provided by Jenkins.  There are hundreds of
      failures, but the engineer is typically interested only in NEW
      failures.  Jenkins JUnit rules typically expect 100% pass rate, or
      some static threshold of failures.
      Specifying test names in the [expected-failures] or [expected-crashes]
      sections of the config file enables JUnit reporting of just the test
      failures which represent new regressions.
      Test names are expected in the dotted JUnit format (eg:
      "piglit.spec.ARB_fragment_program.fp-formats") and are case
      Reviewed-by: default avatarDylan Baker <dylanx.c.baker@intel.com>
  5. 12 Sep, 2014 1 commit
  6. 02 Sep, 2014 1 commit
  7. 27 Aug, 2014 1 commit
  8. 20 Aug, 2014 1 commit
  9. 10 Jul, 2014 3 commits
  10. 23 Jan, 2014 1 commit
    • Tom Stellard's avatar
      cl: Add support for OpenCV unit tests v3 · 4a13528a
      Tom Stellard authored
      This enables piglit to run and interpret the results from OpenCV's
      gtest based opencv_test_ocl program.
      You can enable the OpenCV tests by adding the path to the
      opencv_test_ocl program to your piglit.conf file.
      You can also optionally specify the path to OpenCV's work
      directory if you buid OpenCV in a non-standard way.  For example:
        - Python code cleanups
        - More cleanups
        - Move opencv.py into framework
        - Use ConfigParser
      Reviewed-by: Dylan Baker's avatarDylan Baker <baker.dylan.c@gmail.com>