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
[23.0 backport] builder-next: temporarily disable mergeop and diffop #45112
[23.0 backport] builder-next: temporarily disable mergeop and diffop #45112
Conversation
Looks like changes are needed in the BuildKit integration tests to skip some of these (at least for now);
I expect most of them are because the feature is disabled;
Also seeing a various of "broken pipe" errors;
And some other errors (not sure if they are expected)
|
@thaJeztah Would you be ok with an internal environment variable that makes this pluggable so that tests can continue using this? I wouldn't want to regress on any of the current behavior that the tests are checking. Although I guess it could theoretically also mean that some tests could break only for users, and we don't discover it because tests use env switch. |
Ah, yes, some "DONT USE" env var would work for me |
2a5d679
to
52a6477
Compare
I couldn't add an env without changing the buildkit vendor as well as |
This is green now. |
52a6477
to
da092c4
Compare
The commit message shows the commit on master that was cherry-picked. |
But it wasn't cherry-picked. The master codebase had already (about to be) diverged in this area via #44079 . The original description mentioned this. |
Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> Signed-off-by: Bjorn Neergaard <bneergaard@mirantis.com> (cherry picked from commit 0ac3bf8) Signed-off-by: Bjorn Neergaard <bneergaard@mirantis.com>
Co-authored-by: Tonis Tiigi <tonistiigi@gmail.com> Signed-off-by: Bjorn Neergaard <bneergaard@mirantis.com>
da092c4
to
1363b3e
Compare
Known flake in Windows CI:
|
Temporarily disable Merge/Diff until there is a proper solution to #45111 . Dockerfiles will detect the missing capability for
COPY --link
and fall back to the behavior in 20.10.Changed to be a backport of a change to master for workflow reasons by @neersighted.