-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
x/build: add a builder with oldest git supported by cmd/go to catch regressions #26653
Comments
Git 2.7.4 is notable(?) because it is the stock version in Ubuntu 16.04 LTS.¹ However, it's not obvious to me why we should draw the line at Ubuntu 16.04: the Ubuntu project claims to still support 14.04.5 LTS,² and the current release is 18.04 LTS. (Ubuntu 18.04 LTS provides git 2.17,³ which is much more recent.) I don't actually see a minimum Ubuntu or Git version listed on https://tip.golang.org/doc/install. Perhaps we should add one. (CC: @rsc @rogpeppe @bradfitz @myitcv) ¹https://packages.ubuntu.com/xenial/vcs/git |
I think thats a wonderful idea! |
Whether Ubuntu 14.04 is a sufficiently broad baseline for this sort of analysis I'm not 100% sure (it's pretty good on the basis it's used by Travis); it ships |
My development VM was Debian Jessie for the longest time and its old git (https://packages.debian.org/jessie/git-core ... 2.1.4) was what finally forced me to update to stretch. |
Note also #26594 (comment), which suggests we might also need to add tests for different remote types. |
(Note that Ubuntu 14.04.6 LTS reached the end of its Ubuntu “standard support” lifetime in April 2019.) |
The current version of the standard
Closing as done. (To help keep the issues that are still open more accurate and actionable.) |
@dmitshur, IIRC the request here is to set up a builder with an old |
Indeed, I had misread it, thanks for catching. We can certainly reopen if it's still actionable as is, but as I understand git 2.7.4 is relevant to Ubuntu 16.04 LTS, which passed End of Standard Support in April 2021 (understandably 3 years after this was filed) and so might not be. Since #26746 is accepted by now, we should try to look at this issue when that proposal is implemented. |
Per #26746 (comment), the oldest Git on the builders should be at least |
What did you expect to see?
The bug fix for breaking go on Ubuntu 16 would have a test or ci change to prevent a similar error in the future.
What did you see instead?
A code change with no test change.
Context
#26501 (comment)
The text was updated successfully, but these errors were encountered: