[Bug] Test validator returns Success on empty stdout / runtime error

When submitting code that produces no stdout output (either via stderr only, empty output, or a runtime exception), the test validator occasionally returns Success instead of Failure.

Reproducible with the puzzle “The Helpdesk” or “Insert to String” (maybe with all the puzzles)

Minimal reproduction cases in JavaScript:

  • console.error("".split().map(a=>a)) => outputs to stderr only, stdout empty
  • console.log("".split().map(a=>a)) => outputs [ '' ], not matching expected
  • .map(a=>a) => SyntaxError at runtime, no stdout

In all three cases, the validator intermittently returns Success despite stdout being empty or not matching the expected output, or just being a complete syntax error. The behavior is non-deterministic: the same payload on the same endpoint (/services/TestSession/play) alternates between correct Failure and incorrect Success across consecutive runs without any code change.

This looks like a race condition or stale state on the backend validator when comparing an empty stdout against the expected output.

First time submitting something inside the forum, I don’t know if it’s the correct place / way to do so.

I have something similar when running the test cases in Python. Sometimes the console output gives the following output, regardless if the output provided by my code is correct or not:

  • Standard Output Stream:

    ?GREEN?Success?GREEN?
    

    Success

Running the test case several times in a row will sometimes result in this strange message while most of the time it seems to behave correctly. I have had this with several of the puzzles, so I don’t think this is related to any specific puzzle. Most recently it was with the sum of spirals diagonals puzzle.

Screenshot:

Yeah I’m facing this every time I play Clash of Code.

When running a Test Case, there is a chance of it just succeeding and outputting this instead of actually validating the code.

The same thing is happening to me as well!! (on every clash I play).

It’s been so annoying especially since it appeared on an edge case that I missed on a Reverse puzzle and only scored 80%. And the chance it has been occuring to me has been increasing lately.