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 emptyconsole.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.

