When targeting Node.js, is a duplicated execution tree a known issue? Otherwise I'm going to open a ...

# javascript

[Edoardo Luppi]

When targeting Node.js, is a duplicated execution tree a known issue? Otherwise I'm going to open a new one for this too.
Edit: it's not only a visual thing, tests are executed two times.

[Big Chungus]

Do you use BOTH compiler mode rather than IR or LEGACY?

[Edoardo Luppi]

@Big Chungus nope, only IR

[Big Chungus]

Smells like a bug then

[Artem Kobzar]

@Ilya Goncharov [JB] ^^
Is it something known?

[Ilya Goncharov [JB]]

don’ think so, looks like unknown bug in intellij

[Artem Kobzar]

But, the tests also ran twice

[Ilya Goncharov [JB]]

Ah ok, I see, then it looka like problem in Gradle plugin

[Edoardo Luppi]

Let me verify the run twice better.
I've placed a couple println and I can see them duplicated in the overall execution log.
I'll also use a timestamp to see if it's another visual artifact or not.

[Artem Kobzar]

Also, @Edoardo Luppi could you try to copy your Run command from IDEA and run the command from the terminal? We want to check if the behavior is the same from inside the terminal

[Edoardo Luppi]

@Artem Kobzar in command line it's executed one time only

[Edoardo Luppi]

I think it's only a visual artifact. You can see that the timestamp is exactly the same
IDEA execution log:

> Task :jsTestTestDevelopmentExecutableCompileSync
Test time: 1688386177494
> Task :jsNodeTest





Test time: 1688386177494









BUILD SUCCESSFUL in 4s
18 actionable tasks: 7 executed, 11 up-to-date