Coverage decreased (-1.3%) to 85.294% when pulling e3d9900 on test-ci-runs-on-node-12-14 into 744a79d on master.

@evertonfraga @ryanio any ideas from the CI pros here why Node 14 is failing? 🤔

The first failure I could detect was on this badge update PR: #134. As there wasn't any other code change on that matter, I strongly suspect of an in-range dependency that got recently updated.

Some info:

• The problem occurs after all tests are executed.
• I can't reproduce it locally with Node 14 on Mac.
• The error message "Segmentation fault (core dumped)" comes from C/C++, so either NodeJS core or an extension of it.

I'll keep looking into it.

Locked to the same v14.9.0 node version and had issues as well. Investigating...

Update:

To debunk the hypothesis that a dependency upgrade is causing this issue, I grabbed a package-lock.json generated before the observed failures, and have installed the dependencies from the lockfile using npm ci, but the tests still fail.

Heading back to github actions, the last node-14 green test was using v14.4.0. The failure was introduced along with the image update to 14.9.0.

So right now, I am testing with several node 14.x versions, to better know what version has introduced the segfault to our code.

On another track, I'm trying to detect the root cause, running tests locally.

Extended node versions until 14.13 and the issue persists. I need to give a closer look on local tests.

@evertonfraga ok, thanks for keeping on with this a bit

Looks like the ci is resolving now with all node versions with updated dependencies