delta/glib.git/tests/mainloop-test.c, branch require-python34

all: Remove trailing newlines from g_message()/g_warning()/g_error()s

2018-04-27T15:46:19+00:00

All those logging functions already add a newline to any message they
print, so there’s no need to add a trailing newline in the message
passed to them.

Signed-off-by: Philip Withnall 
Reviewed-by: nobody

Consistently save errno immediately after the operation setting it

2017-08-03T09:21:13+00:00

Prevent the situation where errno is set by function A, then function B
is called (which is typically _(), but could be anything else) and it
overwrites errno, then errno is checked by the caller.

errno is a horrific API, and we need to be careful to save its value as
soon as a function call (which might set it) returns. i.e. Follow the
pattern:
  int errsv, ret;
  ret = some_call_which_might_set_errno ();
  errsv = errno;

  if (ret < 0)
    puts (strerror (errsv));

This patch implements that pattern throughout GLib. There might be a few
places in the test code which still use errno directly. They should be
ported as necessary. It doesn’t modify all the call sites like this:
  if (some_call_which_might_set_errno () && errno == ESOMETHING)
since the refactoring involved is probably more harmful than beneficial
there. It does, however, refactor other call sites regardless of whether
they were originally buggy.

https://bugzilla.gnome.org/show_bug.cgi?id=785577

mainloop-test: Fix uninitialized memory access in tests

2013-11-11T16:35:26+00:00

https://bugzilla.gnome.org/show_bug.cgi?id=711751

mainloop-test: Fix leaks in tests

2013-11-10T21:43:25+00:00

https://bugzilla.gnome.org/show_bug.cgi?id=711751

Remove a bunch of lingering g_thread_init()

2013-06-01T03:03:19+00:00

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.

Fix more warning-addition fallout

2012-11-02T16:27:19+00:00

I'm normally a big fan of small atomic commits, but I also want to get
things done this afternoon...

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=687441
Reviewed-by: Colin Walters

Remove g_mutex_new()/g_cond_new() in testcases

2011-10-04T23:35:27+00:00

These were the last users of the dynamic allocation API.

Keep the uses in glib/tests/mutex.c since this is actually meant to test
the API (which has to continue working, even if it is deprecated).

https://bugzilla.gnome.org/show_bug.cgi?id=660739

Make threads mandatory

2011-09-09T16:41:55+00:00

G_THREADS_ENABLED still exists, but is always defined. It is still
possible to use libglib without threads, but gobject (and everything
above it) is now guaranteed to be using threads (as, in fact, it was
before, since it was accidentally impossible to compile with
--disable-threads).

https://bugzilla.gnome.org/show_bug.cgi?id=616754

[mainloop-test] Fix compilation errors

2010-05-26T20:21:15+00:00

GSource: add g_source_set_name, g_source_get_name, g_source_set_name_by_id

2010-05-25T20:59:22+00:00

These allow applications to give meaningful names to their sources.
Source names can then be used for debugging and profiling, for
example with systemtap or gdb.

https://bugzilla.gnome.org/show_bug.cgi?id=606044