You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
In #2612result, 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)
❔ 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
The text was updated successfully, but these errors were encountered: