From fa29974dabc03479848935168eb4e26becbe304d Mon Sep 17 00:00:00 2001
From: Feoramund <161657516+Feoramund@users.noreply.github.com>
Date: Sun, 2 Jun 2024 23:21:44 -0400
Subject: [PATCH] Use `Warning` log level for reporting memory leaks

Works well with `-define:ODIN_TEST_LOG_LEVEL=warning`.
---
 core/testing/runner.odin | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/core/testing/runner.odin b/core/testing/runner.odin
index 190e10744..c82aa1fda 100644
--- a/core/testing/runner.odin
+++ b/core/testing/runner.odin
@@ -467,16 +467,18 @@ runner :: proc(internal_tests: []Internal_Test) -> bool {
 			when TRACKING_MEMORY {
 				#no_bounds_check tracker := &task_memory_trackers[data.allocator_index]
 
+				memory_is_in_bad_state := len(tracker.allocation_map) + len(tracker.bad_free_array) > 0
+
 				when ALWAYS_REPORT_MEMORY {
 					should_report := true
 				} else {
-					should_report := len(tracker.allocation_map) + len(tracker.bad_free_array) > 0
+					should_report := memory_is_in_bad_state
 				}
 
 				if should_report {
 					write_memory_report(batch_writer, tracker, data.it.pkg, data.it.name)
 
-					pkg_log.info(bytes.buffer_to_string(&batch_buffer))
+					pkg_log.log(.Warning if memory_is_in_bad_state else .Info, bytes.buffer_to_string(&batch_buffer))
 					bytes.buffer_reset(&batch_buffer)
 				}