Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests fail with CMake on x86. #38264

Open
Sunidhi-Gaonkar1 opened this issue Dec 11, 2024 · 3 comments
Open

Tests fail with CMake on x86. #38264

Sunidhi-Gaonkar1 opened this issue Dec 11, 2024 · 3 comments

Comments

@Sunidhi-Gaonkar1
Copy link

Sunidhi-Gaonkar1 commented Dec 11, 2024

What version of gRPC and what language are you using?

v1.68.2

What operating system (Linux, Windows,...) and version?

Ubuntu 22.04.5

What runtime / compiler are you using (e.g. python version or version of gcc)

gcc version 11.4.0

What did you do?

Hi Team,
We are working on building and testing grpc from source using openssl instead of borinngssl using CMake
I was able to build grpc using CMake, but noticed the follwoing test failure for xds_end2end_test.

What did you expect to see?

Test passing successfully.

What did you see instead?

Faced the following test failure:

/grpc/test/cpp/end2end/xds/xds_end2end_test.cc:1118: Failure
Value of: status.error_message()
Expected: matches regular expression "failed to connect to all addresses; last error: (UNKNOWN|UNAVAILABLE): (ipv6:%5B::1%5D|ipv4:127.0.0.1):[0-9]+: (Failed 
to connect to remote host: )?Tls handshake failed \\(TSI_PROTOCOL_FAILURE\\): SSL_ERROR_SSL: error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED(: .*)?"
  Actual: "failed to connect to all addresses; last error: UNKNOWN: ipv4:127.0.0.1:2832: Tls handshake failed (TSI_PROTOCOL_FAILURE): SSL_ERROR_SSL: error:0A000086:SSL routines::certificate verify failed: self-signed certificate"
  

Attaching detailed logs below.
Any pointers regarding this will be helpful.Thank you.
logs_grpc_x86.txt

Anything else we should know about your project / environment?

@matthewstevenson88
Copy link
Contributor

@gtcooke94 Can you take a look at this failure?

@gtcooke94
Copy link
Contributor

Taking a look - looking at the failure, it looks like maybe we are expecting too specific of a string in the status

@matthewstevenson88
Copy link
Contributor

Good eye! Yes agreed, it's likely just the different error string coming from the different SSL library. Maybe we can change the regex / expected string so that we no longer care about anything past SSL_ERROR_SSL? WDYT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants