This test seems to be compiling and passing just fine (when run in isolation), so turning it back on seems like a good idea. To make it pass when run as part of the full ardour test suite, this does remove the WebSockets control surface from the control surfaces test though, as that control surface messes up the event loop of the main thread, which would otherwise cause use-after-free crashes in the session test. |
||
---|---|---|
.. | ||
ardour_websockets.cc | ||
ardour_websockets.h | ||
client.cc | ||
client.h | ||
component.cc | ||
component.h | ||
dispatcher.cc | ||
dispatcher.h | ||
feedback.cc | ||
feedback.h | ||
interface.cc | ||
json.cc | ||
json.h | ||
manifest.cc | ||
manifest.h | ||
message.cc | ||
message.h | ||
mixer.cc | ||
mixer.h | ||
resources.cc | ||
resources.h | ||
server.cc | ||
server.h | ||
state.cc | ||
state.h | ||
transport.cc | ||
transport.h | ||
typed_value.cc | ||
typed_value.h | ||
wscript |