ci: Don't run functional tests in CI yet

Disable the functional tests in the case of meson as well.
They don't seem to work in the CI or take too long.
This needs further investigation. For now let's run them locally and
before each release.

Signed-off-by: Michael Vetter <jubalh@iodoru.org>

.github/workflows/main.yml

@@ -34,13 +34,13 @@ jobs:
             script: ./ci/ci-build.sh
           - flavor: debian
             buildsystem: meson
-            tests: unit+func
+            tests: unit
             omemo: signal
             script: ./ci/ci-meson-build.sh
             omemo_env: libsignal
           - flavor: debian
             buildsystem: meson
-            tests: unit+func
+            tests: unit
             omemo: libomemo
             script: ./ci/ci-meson-build.sh
             omemo_env: libomemo-c

ci/ci-meson-build.sh

@@ -49,7 +49,7 @@ if [[ "$(uname | tr '[:upper:]' '[:lower:]')" == linux* ]]; then
     meson setup build_valgrind ${tests[0]} ${BACKEND_OPT} -Dtests=true -Db_sanitize=address,undefined
     meson compile -C build_valgrind
 
-    meson test -C build_valgrind --print-errorlogs --wrap=valgrind || echo "Valgrind issues detected"
+    meson test -C build_valgrind "unit tests" --print-errorlogs --wrap=valgrind || echo "Valgrind issues detected"
 
     rm -rf build_valgrind
 fi
@@ -66,7 +66,7 @@ do
     meson setup build_run ${features} ${BACKEND_OPT} -Dtests=true
     meson compile -C build_run
     
-    meson test -C build_run --print-errorlogs
+    meson test -C build_run "unit tests" --print-errorlogs
     
     ./build_run/profanity -v
 done