-
Notifications
You must be signed in to change notification settings - Fork 14
[Flake]: Windows integration test timeouts #923
Comments
From chat, @tmatsuo and @coryan say the failure is a manifestation of grpc/grpc#16872 Can we do anything to make the tests fail (quickly) instead of timing out in this case? If not, then I don't think there's anything we can do except wait for the grpc bug to be fixed. |
I think the timeout might caused by MSVC opening a dialog when you get a crash and the code was compiled in debug mode. The answer is to compile in release mode (where you just get a crash) or to disable the "just in time" debugger: |
And these instructions might be relevant too: |
FWIW, my fixes for gRPC on Windows made it to gRPC-1.26.0. I am working on microsoft/vcpkg#9363 which will bring the fixes to our Windows+CMake builds, @scotthart is working on upgrading the Windows+Bazel builds 1.26.0 too. |
This continue to happen, but that should be expected because we have not migrated to 1.26.0 yet: |
The problem does not seem to repeat since we moved to gRPC-1.26.x, if there are no repeats by 2020-05-01 we should close this bug. |
Actually we moved to 1.26.x on #1234, and the bug reported above cannot happen on that version of gRPC (there are no |
We've been seeing some timeouts in the spanner integration tests on windows. I included one successful run and 3 timeout runs. In the timeout runs I see these two lines in the output.
If
CreateFile failed
(source) /unknown file
is the issue and not a red herring, it appears this causes some test cases to fail and others to hang indefinitely, until the timeout occurs. So, theCreateFile
flakiness is one issue, but the tests should also fail quickly in the event of a failure.Note that
failure1
fails inspanner_client_instance_admin_integration_test
, and actually theInstanceAdminClientTest.InstanceConfig
test FAILED while presumablyInstanceAdminClientTest.InstanceIam
was the one that timed out. In the successful cases this test passes in under 2 seconds vs a timeout of 15 minutes.failure2
andfailure3
fail inspanner_client_rpc_failure_threshold_integration_test
which only has a single testRpcFailureThresholdTest.ExecuteSqlDeleteErrors
. This test typically takes ~2 minutes to run vs the timeout of 15 minutes.success
failure 1
failure 2
failure 3
The text was updated successfully, but these errors were encountered: