1. 01 Jun, 2013 8 commits
    • Allison Karlitskaya's avatar
      glib.mk: Rework win32 test support · 16ec6295
      Allison Karlitskaya authored
      Newer versions of automake (~1.13.1) seem to generate some new rules for
      testcases that get tripped up on our use of $(addsuffix) and $(strip) so
      take those out of the definition of TESTS on win32.
      16ec6295
    • Allison Karlitskaya's avatar
      Change a pair of TESTS = to TEST += · 601a00fa
      Allison Karlitskaya authored
      601a00fa
    • Allison Karlitskaya's avatar
      GSettings tests: reverse installed test complexity · e042db0f
      Allison Karlitskaya authored
      Remove the complications that were introduced in an attempt to make the
      gsettings and gschema-compile tests function as installed tests.  These
      tests are designed (in large part for gsettings and entirely for
      gschema-compile) to test the in-tree tools and should not be testing the
      system versions.
      
      In the future we may want to move the use of the in-tree tools from the
      gsettings testcase into the Makefile and install the resulting files,
      allowing this testcase to run against those files, installed.
      e042db0f
    • Allison Karlitskaya's avatar
      Rework the build system for a new tests approach · f9eb9eed
      Allison Karlitskaya authored
      Perform a substantial cleanup of the build system with respect to
      building and installing testcases.
      
      First, Makefile.decl has been renamed glib.mk and substantially
      expanded.  We intend to add more stuff here in the future, like canned
      rules for mkenums, marshallers, resources, etc.
      
      By default, tests are no longer compiled as part of 'make'.  They will
      be built when 'make check' is run.  The old behaviour can be obtained
      with --enable-always-build-tests.
      
      --disable-modular-tests is gone (because tests are no longer built by
      default).  There is no longer any way to cause 'make check' to be a
      no-op, but that's not very useful anyway.
      
      A new glibtests.m4 file is introduced.  Along with glib.mk, this
      provides for consistent handling of --enable-installed-tests and
      --enable-always-build-tests (mentioned above).
      
      Port our various test-installing Makefiles to the new framework.
      
      This patch substantially improves the situation in the toplevel tests/
      directory.  Things are now somewhat under control there.  There were
      some tests being built that weren't even being run and we run those now.
      The long-running GObject performance tests in this directory have been
      removed from 'make check' because they take too long.
      
      As an experiment, 'make check' now runs the testcases on win32 builds,
      by default.  We can't run them under gtester (since it uses a pipe to
      communicate with the subprocess) so just toss them in TESTS.  Most of
      them are passing on win32.
      
      Things are not quite done here, but this patch is already a substantial
      improvement.  More to come.
      f9eb9eed
    • Allison Karlitskaya's avatar
      Remove a bunch of lingering g_thread_init() · 210b1f8b
      Allison Karlitskaya authored
      After this patch, there is but one remaining use of g_thread_init(),
      which is in tests/slice-threadinit.c, a testcase dedicated to testing
      the functionality of gslice across a g_thread_init() boundary.
      
      This testcase is pretty meaningless these days... probably we should
      delete it.
      210b1f8b
    • Allison Karlitskaya's avatar
      Some final g_test_build_filename() porting · e66abbe2
      Allison Karlitskaya authored
      This should be the last users that need to be ported.
      
      For some of the oldschool non-gtester-ified tests, we call g_test_init()
      from main() because it is necessary in order to use
      g_test_build_filename().
      e66abbe2
    • Allison Karlitskaya's avatar
      Move a pair of gobject tests to tests/gobject/ · d7b3e558
      Allison Karlitskaya authored
      testgobject.c and timeloop-closure.c are the only two tests in the
      toplevel tests/ directory that depend on gobject, so move them to
      tests/gobject/ along with the other gobject tests.
      
      Both of these were in noinst_PROGRAMS and not TESTS, so keep them that
      way when we move them.
      d7b3e558
    • Matthias Clasen's avatar
      Split off the gdbus-overflow test · a114e98d
      Matthias Clasen authored
      It is unrealiable under load, and frequently fails in the
      ostree tests. See https://bugzilla.gnome.org/show_bug.cgi?id=701105
      a114e98d
  2. 31 May, 2013 1 commit
  3. 30 May, 2013 5 commits
  4. 29 May, 2013 14 commits
  5. 28 May, 2013 7 commits
  6. 27 May, 2013 5 commits