CI still fails with Node 6 on Windows.

[sainthkh]

❔ Question

I fixed the Windows watcher.stop() test. And there is no problem with that. (#2609 #2612)

But CI still fails with Node 6 on Windows. You can see the single red circle in the middle of other green ones. According to console messages, it seems that the test failed somewhere when testing to auto-install babel and other dependencies.

Now, here's the question:

The support for Node 6 ends on April 2019. In other words, it's less than 100 days and a little more than 2 months.

I can install Node 6 and track problems. But I don't think it's a good idea for me to spend time to support old and rare systems.

How about removing Node 6 tests from our CI?

🔦 Context

CI fails on Windows + Node 6. And it can confuse new contributors.

💻 Code Sample

Azure CI result

🌍 Your Environment

N/A

[sainthkh]

In #2612 result, there are failures in Linux Node 6 and Windows Node 8 after request to localhost.

The message says that they failed because of timeout.

Error message below:

Error: Timeout of 50000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (D:\a\1\s\packages\core\integration-tests\test\hmr.js)

[devongovett]

We are dropping Node 6 in Parcel 2, but until then we should continue to support it or it would be a breaking change.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.