Aws-sdk-cpp: aws-cpp-sdk-core-tests HttpClientTest.TestNullResponse fails

Created on 23 Jan 2019  路  2Comments  路  Source: aws/aws-sdk-cpp

What platform/OS are you using?

amazonlinux docker container
Linux version 4.9.125-linuxkit (root@659b6d51c354) (gcc version 6.4.0 (Alpine 6.4.0) ) #1 SMP Fri Sep 7 08:20:28 UTC 2018

What compiler are you using? what version?

g++ (GCC) 7.3.1 20180303 (Red Hat 7.3.1-5)

What's your CMake arguments?

bash-4.2# cmake ..
-- TARGET_ARCH not specified; inferring host OS to be platform compilation target
-- Building AWS libraries as shared objects
-- Generating linux build config
-- Building project version: 1.7.38
-- Configuring done
-- Generating done
-- Build files have been written to: /home/aws-sdk-cpp/sdk_build/.deps
[ 33%] Built target AwsCCommon
[ 66%] Built target AwsChecksums
[100%] Built target AwsCEventStream
-- Third-party dependencies are installed at: /home/aws-sdk-cpp/sdk_build/.deps/install
-- Zlib include directory: /usr/include
-- Zlib library: /usr/lib64/libz.so
-- Encryption: Openssl
-- Openssl include directory: /usr/include
-- Openssl library: /usr/lib64/libssl.so;/usr/lib64/libcrypto.so
-- Http client: Curl
-- Curl include directory: /usr/include
-- Curl library: /usr/lib64/libcurl.so
-- Considering sqs
-- Updating version info to 1.7.38
-- Custom memory management enabled; stl objects now using custom allocators
-- Configuring done
-- Generating done
-- Build files have been written to: /home/aws-sdk-cpp/sdk_build

Can you provide a TRACE level log? (sanitize any sensitive information)

[ RUN ] HttpClientTest.TestNullResponse
/home/aws-sdk-cpp/aws-cpp-sdk-core-tests/http/HttpClientTest.cpp:30: Failure
Expected equality of these values:
nullptr
Which is: 8-byte object <00-00 00-00 00-00 00-00>
response
Which is: 16-byte object
[ FAILED ] HttpClientTest.TestNullResponse (107 ms)

Most helpful comment

The issue was caused by my ISP, who was returning a search result while trying to connect to a non existing url (http://some.unknown1234xxx.test.aws). I solved it by running a VPN client , thus eliminating my ISP from the loop. All works now !

All 2 comments

The issue was caused by my ISP, who was returning a search result while trying to connect to a non existing url (http://some.unknown1234xxx.test.aws). I solved it by running a VPN client , thus eliminating my ISP from the loop. All works now !

This was happening to me as well while trying to build it in a docker image. I didn't have a VPN client readily available.

My fix was changing the default DNS on my Mac from my ISP's to google's public DNS @ 8.8.8.8

Was this page helpful?
0 / 5 - 0 ratings