-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: unexpected pseudo version (expected v1.0.1-(datetime) but v0.0.0-(datetime)) #26713
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
Comments
|
Looks like we're not fetching enough history by that point:
|
I can reproduce the symptoms by reversing the order of test cases in the |
Anybody with an old (e.g. Ubuntu) |
Change https://golang.org/cl/126956 mentions this issue: |
@bcmills fix doesn't appear to have worked for old git, no:
gives (at the time of writing):
Probably worth getting a builder with "old" ubuntu to run /cc @bradfitz |
Ok, the current patchset (8) passes its test with both Git 2.18.0 and Git 2.7.4. No idea whether it works any further back than that. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?What did you do?
gomoduletest
includes two commits: the first one is taggedv1.0.0
and the second one is not tagged.What did you expect to see?
The contents of
go.mod
should behttps://tip.golang.org/cmd/go/#hdr-Pseudo_versions says that the pseudo tag should be vX.Y.(Z+1). As the first commit is tagged
v1.0.0
, the next commits should be pseudo-versioned asv1.0.1-(datetime)
.What did you see instead?
The text was updated successfully, but these errors were encountered: