[BUG] Node's fetch fails because of the `--jitless` flag about reassure HOT 3 CLOSED

Works nicely with the --enable-wasm flag, thank you!

from reassure.

@Shywim You are right; the --jitless flag clashes with WASM support which is required used by fetch.

Just for clarity, I would recommend not making real network calls in your tests, as they make the tests less predictable and extend their execution time. I assume that you might be using something like MSW to actually mock the fetch though.

The reason for --jitless flag is that we want to remove the usage of optimizing compiler that would negatively impact the stability of measurements through two factors:

1. VM pausing for non-optimized, optimized compilation
2. Changed execution characteristics due to usage of compiled code vs previously interpreted code

Each of these would make the execution times much less stable.

I've investigated some alternatives for that, and there is --no-opt --no-sparkplug option that should turn off Turbo Fan optimizing compiler (--no-opt) and sparkplug non-optimizing compiler. In order to use these instead of --jitless, we would have to enable them either conditionally so you could try them or conduct some testing on their impact on tests for enabling them by default.

from reassure.

@Shywim pls check if the --enable-wasm option to reassure resolves the issue for you.

from reassure.