Different behavior for zero test found on targets

[avila-gabriel]

run this :

gleam new --template javascript jst && gleam new --template erlang erlt; sed -i '6,$d' jst/test/jst_test.gleam erlt/test/erlt_test.gleam; (cd jst && gleam test); ec1=$?; (cd erlt && gleam test); ec2=$?; echo "javascript=$ec1 erlang=$ec2"; rm -rf jst erlt

I guess it was not caught because of the placeholder test that comes with it

[lpil]

Oh dear! Thank you

For the sake of the reader: What is the behaviour for each? I'm not going to run that command I'm afraid, it's complicated enough to hide malware 😁

[avila-gabriel]

command

ow sorry for the scary cmd, I haven't thought of that. I have a task (go-task) that was failing because some task was returning a 1. The tasks where all gleam test at different projects, two of them were empty, and the one targeted at javascript was the one returning 1 instead of 0, like the empty erlang one did. The earlier cmd spawns two gleam projects, clears the placeholder/example test of each, run the tests and point at their exit codes, exposing the difference