From 81a0a79844f952877f23dca680513dcd54d41c6d Mon Sep 17 00:00:00 2001 From: Valentin Rothberg Date: Fri, 10 Dec 2021 15:32:55 +0100 Subject: compat build: adhere to q/quiet Fixes: #12566 Signed-off-by: Valentin Rothberg --- test/apiv2/10-images.at | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'test') diff --git a/test/apiv2/10-images.at b/test/apiv2/10-images.at index e67f559f3..85d4d69ed 100644 --- a/test/apiv2/10-images.at +++ b/test/apiv2/10-images.at @@ -196,12 +196,16 @@ fi curl -XPOST --data-binary @<(cat $CONTAINERFILE_TAR) \ -H "content-type: application/tar" \ --dump-header "${TMPD}/headers.txt" \ - -o /dev/null \ - "http://$HOST:$PORT/v1.40/libpod/build?dockerfile=containerfile" &> /dev/null + -o "${TMPD}/response.txt" \ + "http://$HOST:$PORT/v1.40/build?dockerfile=containerfile&q=true" &> /dev/null if ! grep -q '200 OK' "${TMPD}/headers.txt"; then echo -e "${red}NOK: Image build from tar failed response was not 200 OK (application/tar)" BUILD_TEST_ERROR="1" fi +if grep -E "\"[0-9a-f]{64}\\\n\"" $(jq .stream "${TMPD}/response.txt"); then + echo -e "${red} quiet-mode should only send image ID" + BUILD_TEST_ERROR="1" +fi # Yes, this is very un-RESTful re: Content-Type header ignored when compatibility endpoint used # See https://github.com/containers/podman/issues/11012 -- cgit v1.2.3-54-g00ecf