cc @nodejs/llnode

It seems that --abort-on-uncaught-exception has regressed on Node.js v14 which is why the test is timing out (instead of aborting, the process exits with -1 normally)

It seems that --abort-on-uncaught-exception has regressed on Node.js v14 which is why the test is timing out (instead of aborting, the process exits with -1 normally)

Ah yes, that might cause v14 tests to fail, although I'm pretty sure llnode is broken on v14 since we bumped V8 recently (as in, after the last time we updated things on llnode).

Codecov Report

Merging #368 into master will increase coverage by 0.05%.
The diff coverage is 81.43%.

@@            Coverage Diff             @@
##           master     #368      +/-   ##
==========================================
+ Coverage   78.93%   78.98%   +0.05%     
==========================================
  Files          33       33              
  Lines        4262     4744     +482     
==========================================
+ Hits         3364     3747     +383     
- Misses        898      997      +99     

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fe9a668...e2906bd. Read the comment docs.

From nodejs/node#32981 it seems the bug was introduced from v12.11.0. Is there any progress in the V8 upstream?

I don't think I opened an upstream bug 🤔 I'll check tomorrow and will open one if I haven't yet.

Although tests are passing on v12, so that issue should be unrelated (hopefully)