ci-change: try to prune node-test-binary-windows

[refack]

Tracing CPU usage seems to indicate node-test-binary-windows is eating a lot of CPU, so I tried to find what could be removed, so I removed references to vs2013 (which AFAIK is relevant only for node v4). We still get VS2013 addons testing with node-gyp CI.

https://ci.nodejs.org/job/node-test-binary-windows/jobConfigHistory/showDiffFiles?timestamp1=2018-09-08_19-05-40&timestamp2=2018-09-11_16-45-26

/CC @joaocgreis

[joaocgreis]

Thanks for pinging about this @refack.

VS2013 should not have been removed. Testing v6 built with 2013 is still relevant. Testing addons with v6 and v8 is still very relevant, I don't think the node-gyp job provides nearly enough coverage. We want to ensure the quality of our LTS lines right?

Did you check the workspaces in master and the jenkins-workspace servers? The Windows clean job should keep the workspaces in the agents under control, but it doesn't touch the ones in the workspace servers. If we mark the workspace servers as temporarily offline one at a time and delete all the workspaces for all jobs or just the ones bigger than some size, it might help.

Another option is create several compile and test jobs, and branch according to node major version in the fanned job, but this is more complex and would have to be staged and reviewed with temporary jobs.

@refack let me know if you can revert that and if I should take a look at the workspaces.

[joaocgreis]

Reverted as discussed in IRC. I'll take a look at the workspaces.

[joaocgreis]

@refack can you provide details on how you found that CPU usage was because of node-test-binary-windows? I'd like to keep investigating that. Thanks!

[refack]

@joaocgreis see #1488 (comment)
From: https://ci.nodejs.org/monitoring?part=currentRequests

[joaocgreis]

For reference, the stack is visible at https://ci.nodejs.org/monitoring?part=currentRequests . Thanks!