Garbled text at the end of a failed test run

[BNAndras]

@kotp, I'm seeing some garbled text at the very end of the test runner output. I'm not sure what I'm looking at, but is this something we need to tweak?

[kotp]

That looks like a image, can you write up an alt text for it, or better yet, use a code fenced block?

Just getting back after the wind storm of 2023. Power is still out for some folks, just got reconnected late yesterday.

[kotp]

That looks like a image, can you write up an alt text for it, or better yet, use a code fenced block?

Looks like I found the test you were looking at here.

The portion of the output looks like this:

 {
   "version": 1,
   "status": "fail",
-  "message": "Starting Vader: 1 suite(s), 5 case(s)\n  Starting Vader: /solution/example_syntax_error.vader\n    (1/5) [EXECUTE] year not divisible by 4: common year\n    (1/5) [EXECUTE] (X) Vim(call):E117: Unknown function: LeapYear\n      > command line..function <SNR>22_vader[5]..vader#run[63]..<SNR>24_run[42]..<SNR>24_execute[2]..vader#window#execute[11]..script line 3\n    (2/5) [EXECUTE] year divisible by 4, not divisible by 100: leap year\n    (2/5) [EXECUTE] (X) Vim(call):E117: Unknown function: LeapYear\n      > command line..function <SNR>22_vader[5]..vader#run[63]..<SNR>24_run[42]..<SNR>24_execute[2]..vader#window#execute[11]..script line 3\n    (3/5) [EXECUTE] year divisible by 100, not divisible by 400: common year\n    (3/5) [EXECUTE] (X) Vim(call):E117: Unknown function: LeapYear\n      > command line..function <SNR>22_vader[5]..vader#run[63]..<SNR>24_run[42]..<SNR>24_execute[2]..vader#window#execute[11]..script line 3\n    (4/5) [EXECUTE] year divisible by 400: leap year\n    (4/5) [EXECUTE] (X) Vim(call):E117: Unknown function: LeapYear\n      > command line..function <SNR>22_vader[5]..vader#run[63]..<SNR>24_run[42]..<SNR>24_execute[2]..vader#window#execute[11]..script line 3\n    (5/5) [EXECUTE] year divisible by 200, not divisible by 400: common year\n    (5/5) [EXECUTE] (X) Vim(call):E117: Unknown function: LeapYear\n      > command line..function <SNR>22_vader[5]..vader#run[63]..<SNR>24_run[42]..<SNR>24_execute[2]..vader#window#execute[11]..script line 3\n  Success/Total: 0/5\nSuccess/Total: 0/5 (assertions: 0/0)\n\n\u001b[?1049h\u001b[22;0;0t\u001b[>4;2m\u001b[?1h\u001b=\u001b[?2004h\u001b[?1004h\u001b[24;1H\u001b[?2004l\u001b[>4;m\u001b[?2004h\u001b[>4;2m\u001b[?2004l\u001b[>4;m\u001b[23;2t\u001b[23;1t\r\n\u001b[?1004l\u001b[?2004l\u001b[?1l\u001b>\u001b[?1049l\u001b[23;0;0t\u001b[>4;m"
+  "message": "Starting Vader: 1 suite(s), 5 case(s)\n  Starting Vader: /solution/example_syntax_error.vader\n\u001b[01;32m\u001b[K    (1/5) [EXECUTE] year not divisible by 4: common year\u001b[m\u001b[K\n\u001b[01;32m\u001b[K\u001b[01;31m\u001b[K    (1/5) [EXECUTE] (X) Vim(call):E117: Unknown function: LeapYear\u001b[m\u001b[K\u001b[m\u001b[K\n      > line 3\n\u001b[01;32m\u001b[K    (2/5) [EXECUTE] year divisible by 4, not divisible by 100: leap year\u001b[m\u001b[K\n\u001b[01;32m\u001b[K\u001b[01;31m\u001b[K    (2/5) [EXECUTE] (X) Vim(call):E117: Unknown function: LeapYear\u001b[m\u001b[K\u001b[m\u001b[K\n      > line 3\n\u001b[01;32m\u001b[K    (3/5) [EXECUTE] year divisible by 100, not divisible by 400: common year\u001b[m\u001b[K\n\u001b[01;32m\u001b[K\u001b[01;31m\u001b[K    (3/5) [EXECUTE] (X) Vim(call):E117: Unknown function: LeapYear\u001b[m\u001b[K\u001b[m\u001b[K\n      > line 3\n\u001b[01;32m\u001b[K    (4/5) [EXECUTE] year divisible by 400: leap year\u001b[m\u001b[K\n\u001b[01;32m\u001b[K\u001b[01;31m\u001b[K    (4/5) [EXECUTE] (X) Vim(call):E117: Unknown function: LeapYear\u001b[m\u001b[K\u001b[m\u001b[K\n      > line 3\n\u001b[01;32m\u001b[K    (5/5) [EXECUTE] year divisible by 200, not divisible by 400: common year\u001b[m\u001b[K\n\u001b[01;32m\u001b[K\u001b[01;31m\u001b[K    (5/5) [EXECUTE] (X) Vim(call):E117: Unknown function: LeapYear\u001b[m\u001b[K\u001b[m\u001b[K\n      > line 3\n  Success/Total: 0/5\nSuccess/Total: 0/5 (assertions: 0/0)\n\n\u001b[?2004h\u001b[?1049h\u001b[22;0;0t\u001b[?1h\u001b=\u001b[?2004h\u001b[24;1H\u001b[?2004l\u001b[?2004h\u001b[?2004l\u001b[23;2t\u001b[23;1t\u001b[22;2t\u001b[22;1t\u001b[23;2t\u001b[23;1t\r\n\u001b[?2004l\u001b[?1l\u001b>\u001b[?1049l\u001b[23;0;0t"
 }

[kotp]

These look like ANSI sequence codes for color and "formatting" information. What are we capturing here? The output is "ANSI" coding, and so looks like it is being captured from something that intended to be viewed in a terminal with ANSI capabilities.

[kotp]

It may be coming from jq. Here is a note from the documentation for jq.

      * `--color-output` / `-C` and `--monochrome-output` / `-M`:

        By default, jq outputs colored JSON if writing to a
        terminal. You can force it to produce color even if writing to
        a pipe or a file using `-C`, and disable color with `-M`.
        When the `NO_COLOR` environment variable is not empty, jq disables
        colored output by default, but you can enable it by `-C`.