-
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
Package's ".x" is not reproducible between dependency upgrade #4111
Comments
Forgot to add: I also tried to compile the go_library several times in a loop
and was able to verify that the So the few bytes changes must come from the dependency upgrade, just unclear why. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a tracking issue for golang/go#69547
I was upgrading our external dependencies recently and these 2 GoCompilePkg actions ran on the same package between 2 consecutive commits.
Specifically, the package is
server/util/db
with a single source filedb.go
. The upgraded dependency wasgorm.io/driver/{mysql,clickhouse,sqlite}
. There was no code change in db.go.The expectation is for
db.x
output to stay the same between the 2 compilations as no exported data was change. However, we observed that there were some bytes differences between the 2.x
files, which caused downstream compile actions to all rebuild.I tried using various gcexports tools to decode the 2 files and diff them but the contents are pretty much identical. Consulting upstream Go team for more information on the 7-bytes diff.
The text was updated successfully, but these errors were encountered: