This is related with the new global "timeout" setting in testy.json.
Problem: The yarn task "testyts" is not exiting after the test completion. The task is running at least the timeout time specified in the testy.json file.
I.E. if there is a long timeout defined "timeout": 100000, the task will only exit after this timeout.
This issue brings some disadvantages:
VSCode Test debugger doesn't stop for a long time.
Long execution time for tests
Workarounds:
using a global install of testyts und execute the tests with testyts (why is it working here?) (no VSCode debugging support).
lower the timeout as low you can... (but a deallocated container instance can take some time to come up...)
This is related with the new global "timeout" setting in testy.json.
Problem: The yarn task "testyts" is not exiting after the test completion. The task is running at least the timeout time specified in the testy.json file.
I.E. if there is a long timeout defined
"timeout": 100000
, the task will only exit after this timeout.This issue brings some disadvantages:
Workarounds:
testyts
(why is it working here?) (no VSCode debugging support).