commit fa20746e037e3ca89c52413be8bf9e4febd60cca
author fayang <fayang@google.com> Wed May 06 08:48:53 2020 -0700
committer Copybara-Service <copybara-worker@google.com> Wed May 06 08:49:26 2020 -0700
tree 64a938dcfd563819047e33e8a41e20332414c377
parent 7e34e1a42837e137f1ad7d243b52a5e359c1f93a

Use GetGuaranteedLargestMessagePayload in SendMessages to make it less flaky. GetCurrentLargestMessagePayload maybe 1-byte larger when there is pending frames, and this will be addressed in b/155761918.

PiperOrigin-RevId: 310159563
Change-Id: I49ffc55159a787781040776222f3caf77d198619

quic/core/http/end_to_end_test.cc

diff --git a/quic/core/http/end_to_end_test.cc b/quic/core/http/end_to_end_test.cc
index af52b12..ccbe3af 100644
--- a/quic/core/http/end_to_end_test.cc
+++ b/quic/core/http/end_to_end_test.cc
@@ -3809,7 +3809,7 @@
     for (size_t i = 2; i <= kTestMaxNumberOfMessages; ++i) {
       size_t message_length =
           random->RandUint64() %
-              client_session->GetCurrentLargestMessagePayload() +
+              client_session->GetGuaranteedLargestMessagePayload() +
           1;
       MessageResult result = client_session->SendMessage(MakeSpan(
           client_session->connection()