[tracker-miners] functional-tests: Forbid GStreamer to fork for the registry



commit 045cbfadedeaef135f1558969ec7c9882be1f80b
Author: Carlos Garnacho <carlosg gnome org>
Date:   Thu Mar 7 10:28:32 2019 +0100

    functional-tests: Forbid GStreamer to fork for the registry
    
    Running functional tests in an isolated environment result on gst
    trying to build the registry again, and fork for it. This results
    in a g_spawn call, and who knows why, in this debug line written to
    stdout:
    
    posix_spawn avoided (fd close requested)
    
    This is a g_debug() call from glib which should not end up on screen
    with our verbosity settings, so I'll asume someone else is playing
    smart and replacing the default log handler with something that
    introduces garbage on our stdout.
    
    This notably causes JSON output in video tests to be not quite JSON,
    causing test failures.

 tests/functional-tests/common/utils/extractor.py | 2 ++
 1 file changed, 2 insertions(+)
---
diff --git a/tests/functional-tests/common/utils/extractor.py 
b/tests/functional-tests/common/utils/extractor.py
index bdd305505..38de1da29 100644
--- a/tests/functional-tests/common/utils/extractor.py
+++ b/tests/functional-tests/common/utils/extractor.py
@@ -41,6 +41,8 @@ def get_tracker_extract_jsonld_output(filename, mime_type=None):
     # We depend on parsing the output, so verbosity MUST be 0.
     env = os.environ.copy()
     env['TRACKER_VERBOSITY'] = '0'
+    # Tell GStreamer not to fork to create the registry
+    env['GST_REGISTRY_FORK'] = 'no'
 
     log ('Running: %s' % ' '.join(command))
     try:


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]