29311d4309
Displaying the execution time will aid developers in understanding which test cases are responsible for slow execution times. The test code is already measuring the execution time for every test case, but is not reporting that data anywhere accessible to developers running the tests. The new code will print a TAP comment: # slow test /the/test/path executed in NN.NN secs for any test taking longer than 0.5 seconds to run. Example new output format: $ ./build/glib/tests/unix TAP version 13 # random seed: R02S690dc3c7a04866e4890501eedc7f8eef 1..13 # Start of glib-unix tests ok 1 /glib-unix/pipe # /glib-unix/pipe-stdio-overwrite summary: Test that g_unix_open_pipe() will use the first available FD, even if it?s stdin/stdout/stderr # Bug Reference: https://gitlab.gnome.org/GNOME/glib/-/issues/2795 ok 2 /glib-unix/pipe-stdio-overwrite ok 3 /glib-unix/error ok 4 /glib-unix/nonblocking ok 5 /glib-unix/sighup # slow test /glib-unix/sighup executed in 0.50 secs ok 6 /glib-unix/sigterm # slow test /glib-unix/sigterm executed in 0.50 secs ok 7 /glib-unix/sighup_again # slow test /glib-unix/sighup_again executed in 0.50 secs ok 8 /glib-unix/sighup_add_remove ok 9 /glib-unix/sighup_nested ok 10 /glib-unix/callback_after_signal # slow test /glib-unix/callback_after_signal took 2.00 secs ok 11 /glib-unix/child-wait # Start of get-passwd-entry tests # /glib-unix/get-passwd-entry/root summary: Tests that g_unix_get_passwd_entry() works for a known-existing username. ok 12 /glib-unix/get-passwd-entry/root # /glib-unix/get-passwd-entry/nonexistent summary: Tests that g_unix_get_passwd_entry() returns an error for a nonexistent username. ok 13 /glib-unix/get-passwd-entry/nonexistent # End of get-passwd-entry tests # End of glib-unix tests As a practical usage example, the meson log can be queried to find slow tests project-wide: $ grep 'slow test' build/meson-logs/testlog.txt | sort -n -k 7 -r | head # slow test /threadpool/basics executed in 36.04 secs # slow test /gobject/refcount/properties-3 executed in 30.00 secs # slow test /gio/io-basics executed in 12.54 secs # slow test /timeout/rounding executed in 10.60 secs # slow test /GObject/threaded-weak-ref executed in 10.42 secs # slow test /thread/rerun-all executed in 9.84 secs # slow test /gobject/refcount/object-advanced executed in 5.46 secs # slow test /thread/static-rw-lock executed in 5.00 secs # slow test /gobject/refcount/signals executed in 5.00 secs # slow test /gobject/refcount/signals executed in 5.00 secs Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
GLib
GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.
The official download locations are: https://download.gnome.org/sources/glib
The official web site is: https://www.gtk.org/
Installation
See the file ‘INSTALL.md’. There is separate and more in-depth documentation for building GLib on Windows.
Supported versions
Only the most recent unstable and stable release series are supported. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.
See SECURITY.md for more details.
Documentation
API documentation is available online for GLib for the:
Discussion
If you have a question about how to use GLib, seek help on GNOME’s Discourse
instance. Alternatively, ask a question
on StackOverflow and tag it glib.
Reporting bugs
Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing incoming+gnome-glib-658-issue-@gitlab.gnome.org, but this will give you a degraded experience.
Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums.
In bug reports please include:
- Information about your system. For instance:
- What operating system and version
- For Linux, what version of the C library
- And anything else you think is relevant.
- How to reproduce the bug.
- If you can reproduce it with one of the test programs that are built
in the
tests/subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.
- If you can reproduce it with one of the test programs that are built
in the
- If the bug was a crash, the exact text that was printed out when the crash occurred.
- Further information such as stack traces may be useful, but is not necessary.
Contributing to GLib
Please follow the contribution guide to know how to start contributing to GLib.
Patches should be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123):
Closes: #123
Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.