Windows failures on 10.x

[MylesBorins]

Consistent failures right now

https://ci.nodejs.org/job/node-test-commit-windows-fanned/27379/

Take a look at nodejs/node#27776

I believe this is infrastructure related

14:29:24 > git push "binary_tmp@147.75.70.237:binary_tmp.git" "+jenkins-node-test-commit-windows-fanned-0397aaae4bbe41f46e99dbd30eacface3a696ce8-bin-win-vs2017" 
14:29:25 Warning: Permanently added '147.75.70.237' (ECDSA) to the list of known hosts.
14:29:25 error: refs/heads/jenkins-node-test-commit-windows-fanned-0397aaae4bbe41f46e99dbd30eacface3a696ce8-bin-win-vs2017 does not point to a valid object!
14:30:26 remote: error: refs/heads/jenkins-node-test-commit-windows-fanned-0397aaae4bbe41f46e99dbd30eacface3a696ce8-bin-win-vs2017 does not point to a valid object!        
14:30:26 remote: error: cannot lock ref 'refs/heads/jenkins-node-test-commit-windows-fanned-0397aaae4bbe41f46e99dbd30eacface3a696ce8-bin-win-vs2017': reference already exists        
14:30:26 To 147.75.70.237:binary_tmp.git
14:30:26  ! [remote rejected]       jenkins-node-test-commit-windows-fanned-0397aaae4bbe41f46e99dbd30eacface3a696ce8-bin-win-vs2017 -> jenkins-node-test-commit-windows-fanned-0397aaae4bbe41f46e99dbd30eacface3a696ce8-bin-win-vs2017 (failed to update ref)
14:30:26 error: failed to push some refs to 'binary_tmp@147.75.70.237:binary_tmp.git'
14:30:26 
14:30:26 > if ERRORLEVEL 1 exit /b 

[joaocgreis]

I cleaned the reference, looks like it solved the issue. Thanks for reporting @MylesBorins