Fix: don't use newlines in logging message

[lttng-tools.git] / tests / fast_regression

regression/tools/filtering/test_invalid_filter
regression/tools/filtering/test_unsupported_op
regression/tools/filtering/test_valid_filter
regression/tools/streaming/test_ust
regression/tools/health/test_thread_ok
regression/tools/live/test_ust
regression/tools/live/test_ust_tracefile_count
regression/tools/live/test_lttng_ust
regression/tools/tracefile-limits/test_tracefile_count
regression/tools/tracefile-limits/test_tracefile_size
regression/tools/exclusion/test_exclusion
regression/tools/snapshots/test_ust_fast
regression/tools/snapshots/test_ust_streaming
regression/tools/save-load/test_save
regression/tools/save-load/test_load
regression/tools/save-load/test_autoload
regression/tools/mi/test_mi
regression/tools/wildcard/test_event_wildcard
regression/tools/crash/test_crash
regression/tools/regen-metadata/test_ust
regression/tools/regen-statedump/test_ust
regression/ust/before-after/test_before_after
regression/ust/buffers-pid/test_buffers_pid
regression/ust/multi-session/test_multi_session
regression/ust/multi-lib/test_multi_lib
regression/ust/nprocesses/test_nprocesses
regression/ust/overlap/test_overlap
regression/ust/java-jul/test_java_jul
regression/ust/java-log4j/test_java_log4j
regression/ust/python-logging/test_python_logging
regression/ust/getcpu-override/test_getcpu_override
regression/ust/clock-override/test_clock_override
regression/ust/rotation-destroy-flush/test_rotation_destroy_flush
regression/ust/blocking/test_blocking
regression/ust/test_event_basic
regression/ust/test_event_tracef
regression/ust/test_event_perf