Message added on visualize error on forceful termination

[Ceres6]

Closes #333

[simoneb]

LGTM

[RafaelGSS]

LGTM.

[RafaelGSS]

This fails on windows due to no shell. Can you adjust the test to use process.exit instead?

[Ceres6]

Sure! Done!

[RafaelGSS]

@Ceres6 this keeps failing

[Ceres6]

Sorry, file name mismatch 🤦🏻

[Ceres6]

It seems node 14 handles differently creating a read stream from an unexisting file than 16/18 and therefore no error is brought up and the new test fails.
For the failing node 18 tests in Windows and Ubuntu they are not the new one and don't seem to be related with the changes I made so I'm not sure about what we should do here @RafaelGSS

[RafaelGSS]

You can skip v14 in the tests

[Ceres6]

Should I skip v14 only for that test or in general?

[RafaelGSS]

Should I skip v14 only for that test or in general?

For this test. The v14 support will be only dropped when v14 becomes end-of-life.

[Ceres6]

I'm not being able to skip the test, I was trying with the --grep option of tap but it keeps running all the test no matter what I pass. Any ideas?

[simoneb]

@Ceres6 https://node-tap.org/docs/api/#ttestname-options-function. see skip option

[simoneb]

@Ceres6 I realize you're now busy on something else but it would be good to get this out the door.

[Ceres6]

I will try to find some time in this week to see if I can fix it.

[Ceres6]

Just to be aware. I'm testing with node 18.10 (instead of 18.13) and there are a lot less failing tests. Maybe something has changed in the latest version and now it is receiving SIGABRT instead of logging the output

[RafaelGSS]

@Ceres6 can you rebase on main? See also #393

[Ceres6]

Rebased, I have seen the issue, it's what I thought. Let me know if I can help with that in any way.