Debugging Windows Node 6 CI failures

[xzyfer]

Debugging Windows Node 6 CI failures from #1486.

[Keeo]

You can do it @xzyfer!

[xzyfer]

@saper I have managed to create a reduced test case. I feel like it related to nodejs/node#6160 or some other regressions around requires cache introduced in 6.0.0.

So far I have been able to assert the issue only affects Windows (both 32 and 64 bit). See identical builds on Linux, OSX, and Windows.

I suspect the require cache because my reduced test case requires our native modules twice.

• on Windows w/ Node 6 it's loaded at two different paths
• on Windows w/ Node 5 it's loaded twice at the same path
• on Linux w/ Node 6 it's loaded twice at the same path
• on OSX w/ Node 6 it's loaded twice at the same path

The error only happens in the first scenario.

[xzyfer]

It looks like I was correct about the require cache. Removing the subset in AppVeyor resolved the issue. This is because both the native modules requires are now both

C:\projects\node_modules\node-sass\vendor\win32-ia32-48\binding.nod

Where as with the subset the native module was required first from

C:\projects\node_modules\node-sass\vendor\win32-ia32-48\binding.nod

then secondly from

s:\node_modules\node-sass\vendor\win32-ia32-48\binding.nod

[xzyfer]

Ok I've narrowed this down a bug with require and subst.

mkdir \temp1
cd \temp1
npm install node-sass
subst s: \temp1
node
>require('\temp1\node-sass\vendor\win32-ia32-48\binding.node');
>require('s:\vendor\win32-ia32-48\binding.node');

@saper when you're online can you please confirm this?

[xzyfer]

Confirmed removing the subst get the tests passing in #1512

[xzyfer]

I'm tempted to release v3.7.0 with MSVC PDB files and retroactively compile them once this is fixed in Node.