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
vendor: github.com/moby/buildkit v0.10.3 #43571
Conversation
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 (if green)
https://github.com/moby/moby/runs/6351676790?check_suite_focus=true#step:9:2591
Looks like changes in Triggered a build to test dockerd worker on buildkit repo against |
Confirmed that it's broken upstream so should be fixed on BuildKit: https://github.com/moby/buildkit/runs/6352229776?check_suite_focus=true#step:9:2750 |
full diff: moby/buildkit@v0.10.2...v0.10.3 Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This includes a single fix that only affects the tests, so using a temporary override to update the tests to make CI pass, but keeping the module version to the tagged release. https://github.com/moby/buildkit/compare/v0.10.3..0da740f7d4f782a52b416a44f564ac37504b9ee1 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2ed188a
to
80862d6
Compare
I did a quick rebase, and included a temporary commit that overrides the version that's used in CI (for running the tests); we can remove that when we update to buildkit v0.10.4 (or a newer released version); trying to keep the module version to tagged releases if possible. |
LGTM |
moby/buildkit@v0.10.2...v0.10.3
Signed-off-by: CrazyMax crazy-max@users.noreply.github.com