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 697693 - Some tests fail when CK_FORK=no
Some tests fail when CK_FORK=no
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-10 08:48 UTC by LRN
Modified: 2018-05-04 12:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description LRN 2013-04-10 08:48:09 UTC 
Lack of forking has a number of side-effects. For example, pipelines/vorbisenc.c does this:

    GstElement *sink = gst_bin_get_by_name (GST_BIN (bin), "fakesink0");

more than once, but the number on the element "fakesink" will be "1" for the second test of the batch, not "0".

Please run the testsuite with CK_FORK=no on a platform where all tests pass, and fix the failures introduced by CK_FORK=no.

Otherwise running the testsuite on platforms that have no fork (such as W32) is completely useless, since it's difficult to tell apart nofork-related problems and true w32-only bugs (also, tests may hang up).
Comment 1 Olivier Crête 2018-05-04 12:41:40 UTC 
CK_FORK=no make pipelines/vorbisenc.check passes for me. but other do indeed break. I'll close this as wontfix. Please re-open if you plan to fix this and then we can discuss about enabling this on the CI, for example by enabling tests on a future Windows CI.