0.3.0: Tests only working with pipewire tests

Hi! I'm packaging wireplumber for Arch Linux. When building 0.3.0

  meson --prefix='/usr' \
        --buildtype plain \
        --wrap-mode nodownload \
        -D b_lto=true \
        -D b_pie=true \
        -Dintrospection=enabled \
        build
  ninja -C build

I ran the tests (ninja -C build test). Unfortunately 10 of them fail:

[0/1] Running all tests.
 1/20 test-core                      FAIL           0.50s (killed by signal 6 SIGABRT)
 2/20 test-endpoint                  FAIL           0.55s (killed by signal 6 SIGABRT)
 3/20 test-object-interest           OK             0.02s
 4/20 test-properties                OK             0.02s
 5/20 test-props                     OK             0.02s
 6/20 test-proxy                     FAIL           0.54s (killed by signal 6 SIGABRT)
 7/20 test-session                   FAIL           0.56s (killed by signal 6 SIGABRT)
 8/20 test-session-item              OK             0.03s
 9/20 test-spa-pod                   OK             0.03s
10/20 test-spa-type                  OK             0.02s
11/20 test-transition                OK             0.02s
12/20 test-wptoml                    OK             0.02s
13/20 test-algorithms                OK             0.02s
14/20 test-config-static-objects     FAIL           0.54s (killed by signal 6 SIGABRT)
15/20 test-config-endpoint           FAIL           0.53s (killed by signal 6 SIGABRT)
16/20 test-config-policy             FAIL           0.58s (killed by signal 6 SIGABRT)
17/20 test-dbus-device-reservation   OK             0.08s
18/20 test-si-simple-node-endpoint   FAIL           0.53s (killed by signal 6 SIGABRT)
19/20 test-si-audio-softdsp-endpoint FAIL           0.38s (killed by signal 6 SIGABRT)
20/20 test-si-standard-link          FAIL           0.37s (killed by signal 6 SIGABRT)

Ok:                 10
Expected Fail:      0
Fail:               10
Unexpected Pass:    0
Skipped:            0
Timeout:            0


The output from the failed tests:

I've truncated the overly long output of the failing tests (but they are different from what is being seen in #14 (closed)).

Here's the testlog.txt.

Here are the build/test logs:

• wireplumber-0.3.0-1-x86_64-build.log
• wireplumber-0.3.0-1-x86_64-check.log

I'm wondering, whether it is a requirement for me to have a pipewire compiled with -Dtest=true (as found in your gitlab CI integration) to be able to successfully run the test suite of wireplumber and whether this would have any negative effect on the runtime performance of pipewire.