You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/go/src/github.com/openshift/origin/test/extended/builds/start.go:319
Expected
<bool>: false
to be true
/go/src/github.com/openshift/origin/test/extended/builds/start.go:314
Looks like the build succeeded when we expected it to fail because we didn't supply all the ARGs values that the Dockerfile declared. Did docker change its behavior?
(marking as a flake for now, but this doesn't seem like something that would be intermittent)
The text was updated successfully, but these errors were encountered:
Looks like the message was changed from an error to a warning in v1.13.0-rc1 (moby/moby@f150f42), and also the ', failing build' was removed as it is a warning now instead of an error, I will update the test.
…cker_build_arg_test
Automatic merge from submit-queue (batch tested with PRs 16202, 16198, 16212)
Updating docker --build-arg test due to docker code change
Docker changed the error for a non-existent --build-arg to a warning
and changed the text of the message slightly, breaking one of our tests.
Docker change: moby/moby@f150f42Fixes: #16197
deads2k
pushed a commit
to deads2k/origin
that referenced
this issue
Sep 26, 2017
Docker changed the error for a non-existent --build-arg to a warning
and changed the text of the message slightly, breaking one of our tests.
Docker change: moby/moby@f150f42Fixes: openshift#16197
https://ci.openshift.redhat.com/jenkins/job/test_branch_origin_extended_builds/197
Looks like the build succeeded when we expected it to fail because we didn't supply all the ARGs values that the Dockerfile declared. Did docker change its behavior?
(marking as a flake for now, but this doesn't seem like something that would be intermittent)
The text was updated successfully, but these errors were encountered: