Intermittent EPERM issues using npm link

[darrenscerri]

Am trying to resolve an issue with a build failing for https://github.com/facebookincubator/create-react-app for branch 0.9.x. I've been trying to fix it on my fork https://github.com/darrenscerri/create-react-app.

The build fails nearly every time at the same place, but occasionally passes for the same commit.

Failure:

Pass:

AppVeyor: https://ci.appveyor.com/project/darrenscerri/create-react-app

[FeodorFitsner]

Will take a look.

[FeodorFitsner]

Hi Darren,

I did some tests and got more or less consistent successful results on Visual Studio 2017 image: https://ci.appveyor.com/project/FeodorFitsner/create-react-app/history

I'm not sure about the reason it works "better" on Visual Studio 2017 image - maybe because it's based on Windows Server 2016 and built-in antivirus (Windows Defender) is explicitly disabled there. Maybe it's because of some underlying improvements in Hyper-V hypervisor/drivers (VS 2017 VMs run on Windows Server 2016 DC).

Anyway, you can run on Visual Studio 2017 for now to see if it works better.

[darrenscerri]

Tests are passing now! Thanks for the help Feodor, much appreciated!

[darrenscerri]

Unfortunately, the build from my repo succeeded but the pull request didn't. Noticed that the error is the same error in one of your build while you were trying VS2017. Do you have an idea of what that might be?

[FeodorFitsner]

It might be something module-specific. In the most cases it's racing condition.
Try using retry - we have a special appveyor-retry script that can be used like appveyor-retry npm install.

[darrenscerri]

Ok closing this issue then. Thanks a lot!