1. 17 Dec, 2018 2 commits
  2. 11 Dec, 2018 1 commit
    • Adam Jackson's avatar
      ci: Work around broken python UTF8 handling in the CI docker image · 899d2607
      Adam Jackson authored
      Gitlab very kindly exposes the details of the git commit message (among
      much else) in the environment. Unfortunately, piglit tries to handle the
      environment in non-UTF8-safe ways, which means if the top-of-tree commit
      mentions non-ASCII characters (say, in the author's name) then all the
      tests fail and so does the pipeline.
      
      Fortunately none of those variables are things our piglit invocation
      needs. Since I've failed to rebuild the docker image as yet, just clear
      the likely variables from the environment before running piglit.
      
      This-makes-me: 
      899d2607
  3. 28 Sep, 2016 5 commits
  4. 02 Sep, 2016 1 commit
    • Eric Anholt's avatar
      test: Run some XTS5 integration tests against Xvfb if possible. · deae9c7e
      Eric Anholt authored
      By default the tests will be skipped.  However, if you set XTEST_DIR
      to the repo of a built X Test Suite and PIGLIT_DIR to a piglit repo
      (no build necessary), make check will run piglit's xts-render tests
      against Xvfb.
      
      We could run more of XTS5, but I haven't spent the time identifying
      what additional subset would be worth running, since much of it is
      only really testing the client libraries.  We want to make sure that
      we keep the runtime down, and this subset of the test suite took 92
      seconds according to piglit.
      Reviewed-by: Adam Jackson's avatarAdam Jackson <ajax@redhat.com>
      deae9c7e