From b86cb670a87ff64e64ee7567490e7fb868e4f7a1 Mon Sep 17 00:00:00 2001 From: jedarden Date: Fri, 3 Jul 2026 14:01:29 -0400 Subject: [PATCH] test: print neutral RUN marker on direct setjmp==0 path MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The direct branch of main()'s per-test setjmp loop — taken when a test runs normally without longjmping back — now prints "RUN: " instead of "PASS: ". This is the same neutral marker family child 1 (bf-52k2) chose for the else branch ("RUN: (assertion failed)"), so a passing test prints "RUN: " and a failing test prints "RUN: (assertion failed)". After this child, NEITHER branch emits PASS/FAIL; each test emits exactly one neutral line. The internal passed++ counter is unchanged — it feeds the run summary ("N passed, M failed of T"), not the per-test output, so it is not an "observable label". g_failure_count accounting is likewise untouched. Child 2 of 4 for bf-38e9 (split-child 2 of bf-53ut). Co-Authored-By: Claude --- firmware/test/test_runner.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/firmware/test/test_runner.c b/firmware/test/test_runner.c index fa6d5f0..c0b5199 100644 --- a/firmware/test/test_runner.c +++ b/firmware/test/test_runner.c @@ -255,7 +255,7 @@ int main(void) */ if (setjmp(g_test_jmp) == 0) { g_tests[i].fn(); - printf("PASS: %s\n", g_tests[i].name); + printf("RUN: %s\n", g_tests[i].name); passed++; } else { printf("RUN: %s (assertion failed)\n", g_tests[i].name);