3 Commits

Author	SHA1	Message	Date
Pau Espin	01e0d3e7fd	Drop use of log_set_print_filename() API inside libosmocore ... Let's use log_set_print_filename2() API instead, which has less ackward behavior implications like changing the print status of category-hex. Related: OS#5034 Change-Id: Ifc78e1dcba5baf0b41f6ccbbbd1e3f06552d73da	2021-02-20 17:13:58 +00:00
Pau Espin	690b661fbc	tests: Set print_category values explicitly ... This will alow easily changing default values for print_category vs print_category_hex later. In any case, every test relying on logging output validation should always explicitly state the config to avoid issues in the future if default values change. Related: OS#5034 Change-Id: If29b40557d5c2bcda04b964f344070bad58d8f28	2021-02-20 17:13:58 +00:00
Holger Hans Peter Freyther	c7f52c4c84	wqueue: Reject messges if queue is considered full ... The write queue was always meant to not queue more than the max_length messages but the implementation never rejected a message. Begin to log and enforce the queue size limit, add a testcase to verify the code and initialize except_cb as part of a fix for that new test case. Real applications might now run into the queue limit and drop messages where they just queued them before. It is unfortunate but I still think it is good to implement the routine as it was intended. We need to review osmo_wqueue_enqueue once more to see that no msgb is leaked. Change-Id: I1e6aef30f3e73d4bcf2967bc49f0783aa65395ae	2016-12-09 11:37:37 +01:00