[
https://issues.apache.org/jira/browse/IMPALA-13689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916873#comment-17916873
]
ASF subversion and git services commented on IMPALA-13689:
----------------------------------------------------------
Commit d9476a99c454ca35de8658c2fcb97aa9a61773ff in impala's branch
refs/heads/master from Csaba Ringhofer
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=d9476a99c ]
IMPALA-13689: Fix webserver tests with curl 7.76.1
On Rocky Linux 9.5 a few checks started to fail because error 503
was expected to cause non 0 return value but it was not treated
as error. The difference is likely caused by the newer curl version.
curl documentation seems unclear about the return value of auth
related status codes.
The fix is to check the specific http status code instead of curl's
return value.
Testing:
- webserver tests passed on Rocky Linux 9.5
Change-Id: I354aa87a1b6283aa617f0298861bd5e79d03efc7
Reviewed-on: http://gerrit.cloudera.org:8080/22379
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Some Webserver tests fail with newer curl version
> -------------------------------------------------
>
> Key: IMPALA-13689
> URL: https://issues.apache.org/jira/browse/IMPALA-13689
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Csaba Ringhofer
> Assignee: Csaba Ringhofer
> Priority: Major
>
> This came up in when testing on Rocky 9.5.
> Webserver.TestPostWithSpnego and Webserver.StartWithPasswordFileTest broke
> because for status 403 curl is expected to return non 0 status code. Curl
> documentation doesn't specify how to handle auth errors, even with -f flag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
