Set quic_send_max_push_id_with_settings in some test cases
These test cases don't work with the combination of flags where this flag
is off and the v99 flag is on. (They do work if both are off or both are
on.) The default in chromium is that v99 is on but this flag is off; always
having this flag on fixes the tests for the chromium merge.
gfe-relnote: n/a (flip a flag in some tests)
PiperOrigin-RevId: 283869287
Change-Id: I7b284351df783e781f3070122451d858397dd208
diff --git a/quic/core/http/end_to_end_test.cc b/quic/core/http/end_to_end_test.cc
index c01bbba..df2b458 100644
--- a/quic/core/http/end_to_end_test.cc
+++ b/quic/core/http/end_to_end_test.cc
@@ -3250,6 +3250,7 @@
}
TEST_P(EndToEndTestServerPush, ServerPushUnderLimit) {
+ SetQuicReloadableFlag(quic_send_max_push_id_with_settings, true);
// Tests that sending a request which has 4 push resources will trigger server
// to push those 4 resources and client can handle pushed resources and match
// them with requests later.
@@ -3355,6 +3356,7 @@
}
TEST_P(EndToEndTestServerPush, ServerPushOverLimitWithBlocking) {
+ SetQuicReloadableFlag(quic_send_max_push_id_with_settings, true);
// Tests that when server tries to send more large resources(large enough to
// be blocked by flow control window or congestion control window) than max
// open outgoing streams , server can open upto max number of outgoing
