From c37dce8cfd41281dbdd2f813a2caa4e3b37133f1 Mon Sep 17 00:00:00 2001
From: Eric <5089238+emizzle@users.noreply.github.com>
Date: Wed, 22 Jan 2025 19:22:36 +1100
Subject: [PATCH] format info blurbs

---
 tests/testIntegration.nim | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/tests/testIntegration.nim b/tests/testIntegration.nim
index 38e0e8e8..9738d795 100644
--- a/tests/testIntegration.nim
+++ b/tests/testIntegration.nim
@@ -53,7 +53,8 @@ proc run() {.async.} =
   when DebugTestHarness and enabledLogLevel != LogLevel.TRACE:
     styledEcho bgWhite,
       fgBlack, styleBright, "\n\n  ", styleUnderscore,
-      "ADDITIONAL LOGGING AVAILABILE\n\n", resetStyle, bgWhite, fgBlack, styleBright,
+      "ℹ️  ADDITIONAL LOGGING AVAILABLE ℹ️\n\n", resetStyle, bgWhite, fgBlack,
+      styleBright,
       """
   More integration test harness logs available by running with
   -d:chronicles_log_level=TRACE, eg:""",
@@ -62,8 +63,9 @@ proc run() {.async.} =
 
   when DebugCodexNodes:
     styledEcho bgWhite,
-      fgBlack, styleBright, "\n\n  ", styleUnderscore, "ENABLE CODEX LOGGING\n\n",
-      resetStyle, bgWhite, fgBlack, styleBright,
+      fgBlack, styleBright, "\n\n  ", styleUnderscore,
+      "⚠️ ENABLE CODEX LOGGING ⚠️\n\n", resetStyle, bgWhite, fgBlack,
+      styleBright,
       """
   For integration test suites that are multinodesuites, or for
   tests launching a CodexProcess, ensure that CodexConfig.debug