After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791745 - not immediately clear whether g_test_slow() is in effect by default
not immediately clear whether g_test_slow() is in effect by default
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2017-12-18 17:47 UTC by Simon McVittie
Modified: 2017-12-18 19:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
testutils: Document what happens by default and how to change it (4.09 KB, patch)
2017-12-18 17:47 UTC, Simon McVittie 		committed Details | Review

Description Simon McVittie 2017-12-18 17:47:45 UTC 
Created attachment 365715 [details] [review]
testutils: Document what happens by default and how to change it

It isn't immediately obvious from the descriptions of g_test_slow() and g_test_quick() which one is normally used. The attached patch clarifies this, along with various similar options.
Comment 1 Philip Withnall 2017-12-18 18:47:23 UTC 
Review of attachment 365715 [details] [review]:

Yes please!
Comment 2 Philip Withnall 2017-12-18 19:04:32 UTC 
Pushed to master, thanks.

Attachment 365715 [details] pushed as 95e2800 - testutils: Document what happens by default and how to change it