wireplumber/tests
George Kiagiadakis 7fdbf7ff50 component-loader: activate & register objects through a common code path
Do this in wp_core_load_component() and let the component loaders worry
only about creating the object.

Also run the main loop in tests while loading components, to ensure
that the async operation finishes before continuing execution. GTask
makes sure to make the operation async always, by emitting the callback
from an idle GSource.
2023-05-26 21:22:48 +03:00
..
common log: rename "message" level to "notice" and print criticals with "E" 2023-05-18 16:19:49 +03:00
examples core: change the component arguments to be WpSpaJson instead of GVariant 2023-05-25 18:29:58 +03:00
modules component-loader: activate & register objects through a common code path 2023-05-26 21:22:48 +03:00
scripts default-nodes-tests: use the changed variable in test utils 2023-04-17 07:48:18 -04:00
wp log: implement a log topics system, like pipewire 2023-05-16 20:42:28 +03:00
wplua log: implement a log topics system, like pipewire 2023-05-16 20:42:28 +03:00
meson.build tests: run with WIREPLUMBER_DEBUG=T, not 7... 2023-05-19 21:13:19 +03:00
script-tester.c component-loader: activate & register objects through a common code path 2023-05-26 21:22:48 +03:00