Open dhardtke opened 2 years ago
Maybe this issue belongs in https://github.com/denoland/deno_task_shell?
Another case when spawned process not closed when deno task exit
{
"importMap": "./import_map.json",
"tasks": {
"lume": "echo \"import 'lume/task.ts'\" | deno run --unstable --allow-read --allow-run --lock=lock.json -",
"serve": "deno task lume -s",
"test": "deno task serve --quiet & PUPPETEER_PRODUCT=chrome deno test --no-check --parallel --shuffle=7 --unstable --allow-env --allow-write --allow-read --allow-net --allow-run ; exit"
}
}
This is my deno.json config for running e2e test.
In this example when I run deno task test
, the server is still running although the deno test
is done.
(notice there is ; exit
at the end of line)
Following! Whats the status on this?
I think I'm also running into this – It's possible this is why Deno.serve sometimes and says the address is already in use when in --watch mode (https://github.com/denoland/deno/issues/16699)
For instance, right now my Deno.serve is still running even though I've exited out of the terminal that ran the deno task to start it.
Consider this example:
deno.jsonc:
script.ts:
reproduction.ts:
Here's the behavior using the
BROKEN
cmd inreproduction.ts
:Here's the same execution but this time using the
WORKING
cmd: