Open jespertheend opened 8 months ago
Any chance you could try on latest canary? I think it might have been caused by a PR that was later reverted (but not yet released).
@bartlomieju I'm using Apple Silicon so that means I'd have to build Deno from source. How old is that PR? I've been seeing this for a good few months now but only decided to report this just now. Let me know if you'd still like me to try to build canary.
Oh if you've seen it for months then it's not a recent change.
Could you provide a reproduction so we could test it on our end?
I was worried I wouldn't be able to reproduce it without a large project, but it seems like I'm able to reproduce it with just two files after all!
for (let i=0; i<1000; i++) {
Deno.test({
name: "Test " + i,
fn() {}
})
}
Save this in two files called testA.test.js
and testB.test.js
and run with deno test --parallel
.
I got a whole bunch of logged outputs in there:
Version: Deno 1.40.2
I'm pretty sure the tests aren't logging anything, because it only seems to happen when I run multiple test files with
--parallel
. If I either remove that flag or run only a single file. I'm not seeing any------- output -------
messages logged.This screenshot was taken from this GitHub Actions run.