-
Notifications
You must be signed in to change notification settings - Fork 120
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reduce flakiness of gcs_testbench_test
Previously, gcs_testbench_test could fail to start the storage_testbench for several reasons: 1. Deadline exceeded, especially for AddressSanitizer builds. 2. CURLE_UNSUPPORTED_PROTOCOL error returned from "start_grpc" request, if request is made just while the server is starting. 3. Port is already in use. This commit addresses: - problem (1) by increasing the deadling to 30 seconds; - problem (2) by treating that error as UNAVAILABLE and retrying. - problem (3) by checking if the subprocess has exited and restarting with a new port, and additionally allowing the grpc port to be chosen automatically since the chosen port is returned in the HTTP response. In order to support testing if a process has exited, this adds a a non-blocking option to Subprocess::Join. PiperOrigin-RevId: 561557166 Change-Id: I6cd3fb4dfbaf96cb8a2f3e721ec210d56476f832
- Loading branch information
1 parent
e371f6e
commit f3ed94c
Showing
8 changed files
with
101 additions
and
40 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters