Google Git
Sign in
fuchsia / third_party / glib / 2e3775426199ad3ac4b080251aa23b47d82d4122
commit2e3775426199ad3ac4b080251aa23b47d82d4122[log] [tgz]
authorEmmanuele Bassi <ebassi@gnome.org>Thu Apr 01 14:26:32 2021 +0100
committerPhilip Withnall <pwithnall@endlessos.org>Wed Apr 07 16:36:06 2021 +0100
tree3758a9a9b5ba1dab94de141544f0f606af2aa81b
parent484531600ca39ebabb5f58c397df4f4622d2ebfd [diff]
Split g_test_log() messages that contain multiple lines

When using TAP we want every single line to be one of the following:

 - a valid TAP clause
 - a comment
 - a blank line

Typical explicit test logs are single line comments, but in some cases
we might end up printing debug messages from libraries, and those may
contain multiple lines. When that happens, we break the TAP and fail the
test in conditions entirely outside of our control.

One option to avoid outright failure is to always prepend each line of a
messge with `#`, to ensure that the whole thing is considered a comment.
1 file changed
tree: 3758a9a9b5ba1dab94de141544f0f606af2aa81b
  1. .gitlab-ci/
  2. docs/
  3. fuzzing/
  4. gio/
  5. glib/
  6. gmodule/
  7. gobject/
  8. gthread/
  9. m4macros/
  10. po/
  11. subprojects/
  12. tests/
  13. .clang-format
  14. .dir-locals.el
  15. .gitattributes
  16. .gitignore
  17. .gitlab-ci.yml
  18. AUTHORS
  19. check-abis.sh
  20. clang-format-diff.py
  21. CONTRIBUTING.md
  22. COPYING
  23. glib-gettextize.in
  24. glib.doap
  25. glib.supp
  26. HACKING
  27. INSTALL.in
  28. meson.build
  29. meson_options.txt
  30. msvc_recommended_pragmas.h
  31. NEWS
  32. NEWS.pre-1-3
  33. README
  34. README.md
  35. README.rationale
  36. README.win32
  37. README.win32.md
  38. template-tap.test.in
  39. template.test.in
README.md

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.in’

How to report bugs

Bugs should be reported to the GNOME issue tracking system. (https://gitlab.gnome.org/GNOME/glib/issues/new). You will need to create an account for yourself.

In the bug report 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 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.

Patches

Patches should also 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.