[gnome-initial-setup/wip/wjt/smoke-test] Smoke-test gnome-initial-setup --help




commit 4698ce731ea00f9d45f52ee876ca1c314b9f3f9b
Author: Will Thompson <wjt endlessos org>
Date:   Fri Jul 8 11:18:10 2022 +0100

    Smoke-test gnome-initial-setup --help
    
    Initial Setup is currently crashing on startup in GNOME OS with:
    
        (process:2603): libsoup-ERROR **: 07:05:13.282: libsoup2 symbols
        detected. Using libsoup2 and libsoup3 in the same process is not
        supported.
    
    This is because Initial Setup was built against soup3 and with parental
    controls enabled; unfortunately, malcontent-ui links to libflatpak and
    libostree which are currently built with soup2.
    
    Similar scenarios may occur in the future. In lieu of an actual test
    suite, test that 'gnome-initial-setup --help' succeeds.
    
    https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/513

 gnome-initial-setup/meson.build | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)
---
diff --git a/gnome-initial-setup/meson.build b/gnome-initial-setup/meson.build
index 62b7fd1f..199aeedf 100644
--- a/gnome-initial-setup/meson.build
+++ b/gnome-initial-setup/meson.build
@@ -102,7 +102,7 @@ dependencies = [
     webkitgtk_dep
 ]
 
-executable(
+gnome_initial_setup_exe = executable(
     'gnome-initial-setup',
     sources,
     include_directories: config_h_dir,
@@ -111,6 +111,14 @@ executable(
     install_dir: get_option('libexecdir')
 )
 
+# Smoke-test to ensure the binary actually runs. This catches, for example,
+# transitively linking against two different versions of libsoup.
+test(
+    'gnome-initial-setup--help',
+    gnome_initial_setup_exe,
+    args: ['--help'],
+)
+
 executable(
     'gnome-initial-setup-copy-worker',
     ['gnome-initial-setup-copy-worker.c'],


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