-
Notifications
You must be signed in to change notification settings - Fork 653
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] Null Exception #2825
Comments
This will be impossible to debug without access to the repository that is failing. Is it public? If not, are you able to reproduce the problem in a public repository? |
This is not a public repository. I have not tried it on any public
repository.
It fails in the gitlab repository where there is a build branch for the
builds.
…On Tue, Aug 31, 2021 at 2:55 AM Asbjørn Ulsberg ***@***.***> wrote:
This will be impossible to debug without access to the repository that is
failing. Is it public? If not, are you able to reproduce the problem in a
public repository?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2825 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACNJ2MTASMO25I6LHQLXASDT7SRIRANCNFSM5C4VW5DA>
.
|
I had a similar bug also on a private repo I debugged gitversion and the source of the problem seemed to be here a merge base wasn't found so when it tries to construct a new Commit using null it crashes. I fixed it by passing in some config to make the search for a merge base return successfully. I wonder if the wildcard regex search for a merge base is deterministic across clones of the repo though which is maybe why this happens to some people but not others (looking at some of the other issues that mention similar crashes). |
That sounds probable, @jscarrott. Thanks for debugging the issue. If you figure out a workaround, I'd love to merge a pull request fixing this. |
@asbjornu If you want to provide me a debug build, then I can run on the repository and provide the logs. |
@sanjivpurohit, I don't think we have debug builds readily available. Is it possible for you to fork GitVersion and build it locally yourself? Then you can set breakpoints in the code as well. |
I have a public repo where I ran into this bug if you want to check it out. I am not using any config file. I am using the GitFlow branching style and running the GitVersion action on the master branch works fine, but when I create a Sorry all, looks like my issue was just ignorance. I didn't checkout with a depth of 0. |
I have a reproducer on a public repository: https://github.com/Cray-HPE/cray-product-catalog/runs/4230181725?check_suite_focus=true |
I should note that I attempted this in our Jenkins pipeline as well, and got the same error. Using |
I am still getting the same error in the pre-release version.
|
Thanks for providing a public repository, @rkleinman-hpe. However, I'm unable to reproduce the problem on Are you able to provide a commit and branch that consistently fails? |
|
@sanjivpurohit, your latest stack trace is different from the first you and @rkleinman-hpe posted. As far as I can tell, the first stack trace fails here:
While the second fails here:
We should of course try to fix both errors, but I don't think they are related. |
I have started exploring possible fixes for this in #3064. Please add your thoughts, ideas and feedback if you have any. |
I tried the latest build and there are still more null protection required. Please let me know if you want me to open new issue. |
🎉 This issue has been resolved in version 5.10.0 🎉 Your GitReleaseManager bot 📦🚀 |
Describe the bug
Error: The process '/opt/hostedtoolcache/GitVersion.Tool/5.7.0/x64/dotnet-gitversion' failed with exit code 1
Expected Behavior
output JSON
Actual Behavior
Error: The process '/opt/hostedtoolcache/GitVersion.Tool/5.7.0/x64/dotnet-gitversion' failed with exit code 1
Possible Fix
Steps to Reproduce
Context
I can't use gitversion in my CI/CD
Your Environment
The text was updated successfully, but these errors were encountered: