increase timeout for windows C++ distribtests#32669
Merged
jtattermusch merged 1 commit intogrpc:masterfrom Mar 22, 2023
Merged
Conversation
veblush
approved these changes
Mar 21, 2023
jtattermusch
added a commit
to jtattermusch/grpc
that referenced
this pull request
Mar 24, 2023
After switching to grpc-win2019 kokoro image, the windows C++ distribtest got slightly slower (from about ~1500sec to ~1650sec), which got us too close to the 1800sec time limit and thus we've seen the windows distribtests occasionally time out. I'd still like to look into speeding up the distribtests, but for now we don't want frequest test timeouts in the CI. example failure: https://fusion2.corp.google.com/ci;ids=1923284992/kokoro/prod:grpc%2Fcore%2Fmaster%2Fwindows%2Fgrpc_distribtests_standalone/activity/996fd2cf-bef3-4490-85da-a52765d84127/log ``` 2023-03-20 23:43:44,740 TIMEOUT: distribtest.cpp_windows_x86_cmake_as_externalproject [pid=5984, time=1800.1sec] ```
jtattermusch
added a commit
that referenced
this pull request
Mar 24, 2023
XuanWang-Amos
pushed a commit
to XuanWang-Amos/grpc
that referenced
this pull request
May 1, 2023
After switching to grpc-win2019 kokoro image, the windows C++ distribtest got slightly slower (from about ~1500sec to ~1650sec), which got us too close to the 1800sec time limit and thus we've seen the windows distribtests occasionally time out. I'd still like to look into speeding up the distribtests, but for now we don't want frequest test timeouts in the CI. example failure: https://fusion2.corp.google.com/ci;ids=1923284992/kokoro/prod:grpc%2Fcore%2Fmaster%2Fwindows%2Fgrpc_distribtests_standalone/activity/996fd2cf-bef3-4490-85da-a52765d84127/log ``` 2023-03-20 23:43:44,740 TIMEOUT: distribtest.cpp_windows_x86_cmake_as_externalproject [pid=5984, time=1800.1sec] ```
wanlin31
pushed a commit
that referenced
this pull request
May 18, 2023
After switching to grpc-win2019 kokoro image, the windows C++ distribtest got slightly slower (from about ~1500sec to ~1650sec), which got us too close to the 1800sec time limit and thus we've seen the windows distribtests occasionally time out. I'd still like to look into speeding up the distribtests, but for now we don't want frequest test timeouts in the CI. example failure: https://fusion2.corp.google.com/ci;ids=1923284992/kokoro/prod:grpc%2Fcore%2Fmaster%2Fwindows%2Fgrpc_distribtests_standalone/activity/996fd2cf-bef3-4490-85da-a52765d84127/log ``` 2023-03-20 23:43:44,740 TIMEOUT: distribtest.cpp_windows_x86_cmake_as_externalproject [pid=5984, time=1800.1sec] ```
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After switching to grpc-win2019 kokoro image, the windows C++ distribtest got slightly slower (from about ~1500sec to ~1650sec), which got us too close to the 1800sec time limit and thus we've seen the windows distribtests occasionally time out.
I'd still like to look into speeding up the distribtests, but for now we don't want frequest test timeouts in the CI.
example failure:
https://fusion2.corp.google.com/ci;ids=1923284992/kokoro/prod:grpc%2Fcore%2Fmaster%2Fwindows%2Fgrpc_distribtests_standalone/activity/996fd2cf-bef3-4490-85da-a52765d84127/log