1. 30 Sep, 2014 1 commit
  2. 29 Sep, 2014 1 commit
  3. 06 Sep, 2014 1 commit
  4. 29 Aug, 2014 2 commits
  5. 25 Jul, 2014 1 commit
  6. 24 Jul, 2014 1 commit
  7. 23 Jul, 2014 3 commits
  8. 21 Jul, 2014 1 commit
    • Chris Wilson's avatar
      Use SIGTERM in replace of SIGQUIT · 4f7d4dca
      Chris Wilson authored
      SIGTERM is the normal signal to use when instructing a process to exit.
      The only difference is that an unhandled SIGQUIT is meant to generate a
      coredump, which is not what we want, but in practice I encountered an
      issue where SIGTERM seemed to be deliverable more reliably than SIGQUIT
      (in tests using multiple signal helpers).
      Signed-off-by: Chris Wilson's avatarChris Wilson <chris@chris-wilson.co.uk>
      4f7d4dca
  9. 14 Jul, 2014 2 commits
  10. 13 Jun, 2014 2 commits
  11. 14 May, 2014 2 commits
  12. 22 Mar, 2014 3 commits
  13. 14 Mar, 2014 1 commit
  14. 13 Mar, 2014 1 commit
    • Daniel Vetter's avatar
      lib: add igt_vlog to print varargs · bd53d722
      Daniel Vetter authored
      ... and put it to immediate use in igt_display_log.
      
      To make this all add up also drop the return value of igt_display_log,
      no one really cared anyway.
      
      Aside: I've noticed that every time another subtest runs (at least
      with kms_pipe_crc_basic) the log indent level moves one up ...
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      bd53d722
  15. 12 Mar, 2014 3 commits
    • Daniel Vetter's avatar
      lib/igt_core: api documentation · 55e64989
      Daniel Vetter authored
      At most a bit of comment of function declaration movement for more
      polish. One tricky bit is to #ifdef out (only for gtkdoc of course)
      the struct option; forward declaration - gtkdoc needlessly lists it.
      
      FIXME: The struct documentation for igt_helper_process somehow doesn't
      get picked up ... Same issue seems to be with the igt_log_level enum,
      I've shoveled the relevant documentation into igt_log in free-form for
      now.
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      55e64989
    • Daniel Vetter's avatar
      lib: extract igt_core.c · d63fe151
      Daniel Vetter authored
      Same game as with ioctl_wrappers.c.
      
      To split was rather clean except for the static function
      oom_adjust_for_doom. But that was a bug, the calls to it in the
      various open helpers should simply be done at init and fork time.
      Which was already the case, except for simple testcase.  So fix it up.
      
      While at it also start with a small section header for the
      documentation.
      
      v2: Don't forget to update the xml template ...
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      d63fe151
    • Daniel Vetter's avatar
      lib/ioctl_wrappers: api doc · 556c49f2
      Daniel Vetter authored
      Also some tiny polish to function interface:
      - @caching in gem_set_tiling should be uint32_t to match the ioctl
        struct.
      - s/size/length/ for gem_write/read.
      - move gem_get_num_rings to the other ring feature helpers.
      
      v2: Also demote gem_require_ring from static inline and move it, too.
      
      v3: Also move gem_handle_to_libdrm_bo.
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      556c49f2
  16. 11 Mar, 2014 2 commits
  17. 13 Feb, 2014 1 commit
    • Daniel Vetter's avatar
      lib: (somewhat) structured logging support · eebdf7f9
      Daniel Vetter authored
      Apparently there's a bit a need for more verbose output in testcases,
      mostly for debugging purposes. At least gem_reset_stats and pm_rps
      have a verbose mode.
      
      On top of that we're currently not taking advantage of piglit's "warn"
      state all that much. But I think it might be useful for testcases which
      are notorious for some kinds of spurious failures, like e.g. the really
      nasty timing checks in kms_flip. If we demote some of them to just
      warnings we could run the overall tests more often.
      
      Hence this patchs adds a new igt_log function with the three levels DEBUG,
      INFO and WARN. Plus a bunch of convenience helpers to keep the test
      code tidy.
      
      The level can be set through an enviroment vairable IGT_LOG_LEVEL with
      info being the default. Also tests can look at the selected log level in
      case they want to run costly debug functions only when needed.
      
      Comments highly welcome, I plan to roll this out over tests which can
      use it (not all, imo that's too much churn) once we've settled on the
      interfaces/semantics.
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      eebdf7f9
  18. 11 Feb, 2014 2 commits
  19. 06 Feb, 2014 1 commit
  20. 19 Jan, 2014 2 commits
  21. 10 Dec, 2013 1 commit
  22. 05 Dec, 2013 1 commit
  23. 27 Nov, 2013 2 commits
  24. 12 Nov, 2013 2 commits
  25. 01 Nov, 2013 1 commit
    • Daniel Vetter's avatar
      lib: add igt_main macro · 071e9ca1
      Daniel Vetter authored
      In the past new testcases with subtest often forgot to add the call to
      igt_exit at the end of their main() function. That is now caught with
      a bit more obnoxious asserts, but it's still a nuissance.
      
      This little igt_main macro takes care of that (and also of calling the
      subtest machinery initialization code correctly).
      
      If no one objects I'll roll this out for all the simple cases (i.e.
      those tests that don't have additional argv parsing on top of the
      subtest machinery).
      
      v2: Roll it out across the board.
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      071e9ca1