1. 23 May, 2017 1 commit
  2. 10 Apr, 2017 1 commit
  3. 01 Sep, 2015 1 commit
    • Emmanuele Bassi's avatar
      Drop binary checks when cross-compiling · 5ce70917
      Emmanuele Bassi authored
      We don't need to run binaries we just built in order to successfully
      build GLib and friends any more.
      Since commit b74e2a72, we don't need to run glib-genmarshal when building
      GIO; since commit f9eb9eed, all our tests (including the ones that do
      need to run binaries we just built) are only built when running "make
      check", instead of unconditionally at every build.
      This means that we don't need to check for existing, native binaries
      when cross-compiling, and fail the configuration step if they are not
      found — which also means that you don't need to natively build GLib for
      your toolchain, in order to cross-compile GLib.
      We can also use the cross-compilation conditional, and skip those tests
      that require a binary we just built in order to build.
  4. 30 Jul, 2014 1 commit
  5. 31 Jan, 2014 1 commit
  6. 19 Nov, 2013 1 commit
  7. 11 Nov, 2013 8 commits
  8. 28 Sep, 2013 1 commit
  9. 20 Sep, 2013 1 commit
    • Ray Strode's avatar
      tests: add signal disconnection test · 29ef8217
      Ray Strode authored
      This commit adds a test to ensure that during a signal emission, if
      a signal handler gets disconnected, it won't be run, even if it would
      have run before the disconnection.
  10. 01 Jun, 2013 4 commits
    • Allison Karlitskaya's avatar
      Change a pair of TESTS = to TEST += · 601a00fa
      Allison Karlitskaya authored
    • 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.
    • 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.
    • 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.
  11. 24 May, 2013 4 commits
  12. 21 May, 2013 3 commits
  13. 07 Feb, 2013 1 commit
  14. 03 Feb, 2013 1 commit
  15. 04 Jan, 2013 2 commits
  16. 18 Dec, 2012 2 commits
  17. 05 Nov, 2012 1 commit
    • Allison Karlitskaya's avatar
      gtype: disallow adding interfaces after the fact · d6a075b0
      Allison Karlitskaya authored
      Add a check to prevent adding an interface to a class that has already
      had its class_init done.
      This is an incompatible change but it is suspected that there are not
      many users of this functionality.  Two known exceptions are pygobject
      (fixed in bug 686149) and our own testsuite (affected tests have been
      temporarily disabled by this patch).
      Once we confirm that nobody else is using this functionality we can
      remove a rather large amount of code for dealing with this case.
  18. 02 Nov, 2012 3 commits
  19. 16 Oct, 2012 1 commit
  20. 30 Apr, 2012 1 commit
  21. 02 Mar, 2012 1 commit