-
Notifications
You must be signed in to change notification settings - Fork 649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Build failing with "failed to write reference" error #2593
Comments
Any idea what else I can check to get around this? Any command I could run to log more details? I have no idea what is wrong on the repository structure that is causing it. |
A public repository that portrays the same error would be the only way I can assist you in finding the source of this bug. |
Hi @asbjornu Was able to fix it on this repository. One of the differences between this was that on the others I already had workaround the #1381 issue with /maxcpucount:1 on the build/package commands. Applying the same workaround here seems to have fixed this as well, so it looks like a concurrency issue again :( I can't really share the repository but I does not have anything special in terms of structure: just a solution with 3 library projects and 1 test project. |
Thanks for the information. Sounds like a race condition that #2581 should have helped remedy, but perhaps this is in another code path. |
Today I got hit by this too -- out of the blue. Using GitLab-CI on Linux containers in Kubernetes. |
Since you saw the error being fixed, @jbaehr, and we haven't received any other reports of this error, I'm closing this as fixed. Please comment if you experience this again and I'll reopen. |
Describe the bug
I'm trying to update from GitVersionTask 5.5.1 to GitVersion.MsBuild 5.6.6 and the builds fail on my Azure DevOps pipeline.
It doesn't seem to happen on all repositories. Was able to update one successfully but fails on another.
The error I get is
LibGit2Sharp.NameConflictException: failed to write reference 'refs/heads/pull/53/merge': a reference with that name already exists.
I cannot replicate it with a local checkout of the branch nor on Azure if the requested build if for the branch instead of the pull request.
Expected Behavior
The build to work in PR on Azure DevOps
Actual Behavior
Fails with failed to write reference error in PR
Steps to Reproduce
Not sure how to reproduce the issue with a simple example.
Found an old issue that talked about the branch names being case sensitive but it does not seem to apply since only the PR build has issues.
Here is the log context:
The text was updated successfully, but these errors were encountered: