This is an automated email from the ASF dual-hosted git repository.
alexey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git
The following commit(s) were added to refs/heads/master by this push:
new b1309119f unset *_proxy env variables for Python3 tests
b1309119f is described below
commit b1309119f2988243a0e239861f1dac33a869f5bd
Author: Marton Greber <[email protected]>
AuthorDate: Mon Jun 26 12:41:55 2023 +0200
unset *_proxy env variables for Python3 tests
Commit 459207ff5c103e7d4d60d974504eb8633e188d15 did unset all proxies in
the Jenkins build & test script. It does so in the Python2 part of the
script. Usually we test for both Python2 and Python3, thus the effect of
the unsets in the Python2 part carry over to the Pytho3 section.
However, if someone runs the build script with only Python3 the
proxies are not unset. This patch unsets all proxies in the Python3 part
as well.
Background: I tend to use build-and-test.sh for development because of
convenience reasons. I was working on RHEL9 nodes, where Python2 is not
present. Having the weird network config, I stumbled upon the original
403 error code issue, as build-and-test.sh with only Python3 enabled did
not unset all the proxies.
Change-Id: If23d310ca0cf9cb9dbda60f32a3f675297ffc28e
Reviewed-on: http://gerrit.cloudera.org:8080/20119
Tested-by: Kudu Jenkins
Reviewed-by: Attila Bukor <[email protected]>
Reviewed-by: Zoltan Chovan <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>
---
build-support/jenkins/build-and-test.sh | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/build-support/jenkins/build-and-test.sh
b/build-support/jenkins/build-and-test.sh
index c6f0ce774..8f6d8c74e 100755
--- a/build-support/jenkins/build-and-test.sh
+++ b/build-support/jenkins/build-and-test.sh
@@ -739,6 +739,17 @@ if [ "$BUILD_PYTHON3" == "1" ]; then
CC=$CLANG CXX=$CLANG++ python setup.py build_ext
set +e
+ # A testing environment might have HTTP/HTTPS proxy configured to proxy
+ # requests even for 127.0.0.0/8 network or other quirks. Since some Python
+ # Kudu tests rely on Kudu components listening on 127.0.0.0/8 addresses,
+ # let's unset environment variables that might affect behavior of the
+ # Python libraries like urllib/urllib2.
+ unset ALL_PROXY
+ unset HTTP_PROXY
+ unset HTTPS_PROXY
+ unset http_proxy
+ unset https_proxy
+
# Run the Python tests. This may also involve some compiler work.
if ! CC=$CLANG CXX=$CLANG++ python setup.py test \
--addopts="kudu --junit-xml=$TEST_LOGDIR/python3_client.xml" \
