CI: Enable installation_iojs test suit in GitHub Actions

[jwagantall]

No description provided.

[jwagantall]

@ljharb , looks like this test suit is passing without issues, except for the v0.40.0 tests that have been failing for a while in production.

Is there anyone looking into those?

[ljharb]

Those are expected to fail forever, since v0.40.0 won't ever have the bug fixed.

[jwagantall]

Those are expected to fail forever, since v0.40.0 won't ever have the bug fixed.

Thank you!

On regards to the Travis failure: https://app.travis-ci.com/github/nvm-sh/nvm/jobs/628361855

Looks like this failure is the same than the one I just started seeing in the slow test suits. It just started happening and is not an issue with the node version since the same stable version was passing a week before..

I'm gonna continue looking and see if this is something related to anything else.. :(

[ljharb]

I think it's a legit failure in both suites, though - these tests talk to the network and the registry and can have their results change over time, legitimately.

[jwagantall]

I think it's a legit failure in both suites, though - these tests talk to the network and the registry and can have their results change over time, legitimately.

Actually, I was looking into them a little more and these are indeed legitimate failures I started seeing today in the slow test suit.

Even if this change is meant for "installation_iojs", so we need to make sure the slow tests are passing in TravisCI before we could merge this change?

[ljharb]

It would be ideal for maximum confidence to have them passing in travis as well, yes, if only to figure out the cause of the failure conclusively.

[jwagantall]

It would be ideal for maximum confidence to have them passing in travis as well, yes, if only to figure out the cause of the failure conclusively.

So,,, looking more into this, I noticed that we are installing the latest versions of node and npm but when I look at the errors we get in the slow test suit, I noticed it is reported in an older version of node:
npm ERR! node v5.10.1
npm ERR! npm v3.8.3

Sorry I am not very familiar with node, but is this test expected to not use the latest version of these packages?

[ljharb]

I'm seeing the same failure on master, fwiw. that particular tests is indeed supposed to be installing node v5.10.1.

The new failure seems to be from running npm install jspm@'<2' -g - i added the <2 in ee9e565.

There's probably no reason the test needs to use any given node version, so let me try to update it in master.