-
Notifications
You must be signed in to change notification settings - Fork 29.7k
install goldctl in docker build #46640
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
install goldctl in docker build #46640
Conversation
c7c80da to
f5ce156
Compare
f5ce156 to
b68ff17
Compare
|
Is this PR still relevant? Or should we close it? |
|
@goderbauer yes, still relevant, I think I can land this soon :) |
|
FYI @kjlubick |
Piinks
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! This is great! Thanks!
I checked the Gold dashboard for results from this PR and all of the linux ones are accounted for (see here).
|
This would pin us at a specific version for Linux shards, but not Mac and Windows. My only concern is if having multiple versions across tests shards will create an issue, I would defer to @kjlubick. |
|
goldctl doesn't change all that often and if it does, I try to backward compatible. I don't envision an issue, unless the Docker image is rarely re-built/updated. |
|
@kjlubick sounds good. For posterity's sake, if in the future there is a breaking change to |
Description
This moves the downloading and installing of
goldctltodev/ci/docker_linux/Dockerfilefor the Cirrus linux tests. Previously, 10 Linux shards were running theinstall_goldctl.shscript as part of their "main" step. This speeds up running of tests and avoids occasional failure to download the tool, as seen in #44786.Related Issues
Fixes #44786
Tests
I did not change any tests as my changes are exercised by the existing framework tests, which depend on
goldctlbeing installed on the host to conduct goldens tests.Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.