Skip to content

Mysterious SymInitialize failure when running tests using Bazel RBE on Windows  #24178

@veblush

Description

@veblush

What version of gRPC and what language are you using?

gRPC C++

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

Windows / Bazel-RBE

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

HEAD

What did you do?

Running test

  • Bazel RBE Windows Debug C/C++
  • Bazel RBE Windows Opt C/C++

What did you expect to see?

Passed

What did you see instead?

Following tests failed

  • //test/core/client_channel/resolvers:dns_resolver_connectivity_using_native_resolver_test
  • //test/cpp/qps:qps_json_driver_test_cpp_generic_async_streaming_qps_unconstrained_insecure
  • //test/cpp/qps:qps_json_driver_test_cpp_protobuf_async_streaming_from_client_1channel_1MB
  • //test/cpp/qps:qps_json_driver_test_cpp_protobuf_sync_streaming_qps_unconstrained_insecure

Error message: (note that 2147483653 = 0x80000005)

[symbolize_win32.inc : 53] RAW: SymInitialize() failed: 2147483653

When rerunning tests after renaming these tests, failing tests changed like

  • //test/cpp/qps:qps_jd_cpp_generic_async_streaming_qps_unconstrained_2waysharedcq_insecure
  • //test/cpp/qps:qps_jd_cpp_protobuf_async_streaming_from_client_qps_unconstrained_insecure
  • //test/cpp/qps:qps_jd_cpp_protobuf_async_streaming_from_server_qps_unconstrained_insecure
  • //test/cpp/qps:qps_jd_cpp_protobuf_async_streaming_qps_unconstrained_2waysharedcq_insecure

This is not like that tests with a long name fail because there were other tests with way longer one. But it seems like that tests with 89 or 90 length of the name tend to fail.

Example of failure:

internal b/169902891

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions