tree ae33cb8902430dbd78559f98dfb1b156f958019a
parent 149b7e62d395d82ef53c948262cf0ab3e84b4236
author awillia <awillia@google.com> 1720457220 -0700
committer Copybara-Service <copybara-worker@google.com> 1720457287 -0700

Improve QuicConnectionTest test times

Certain QuicConnectionTest tests result in warnings like the following:

```
GMOCK WARNING:
../../net/third_party/quiche/src/quiche/quic/core/quic_connection_test.cc:2609: Actions ran out in EXPECT_CALL(*send_algorithm_, OnPacketSent(_, _, _, _, _))...
Called 2 times, but only 1 WillOnce() is specified - returning directly.
Stack trace:
...
```

Stack trace symbolization takes a long time in Chromium unit tests (see https://crbug.com/340987671), so avoiding these warnings reduces the test execution times from seconds to a few milliseconds. IIUC the changes in this CL don't affect the test behavior and just suppress the warnings.

Affected tests with test execution times from my gLinux cloudtop:

 - NoNonProbingFrameOnAlternativePath (41385 ms)
 - ReceivePathProbingFromNewPeerAddressAtServer (9948 ms)
 - ClientResponseToPathChallengeOnAlternativeSocket (2266 ms)
 - DuplicateAckCausesLostPackets (1991 ms)
 - PathValidationOnNewSocketSuccess (2241 ms)
 - PathValidationReceivesStatelessReset (2289 ms)
 - SendPathChallengeUsingBlockedNewSocket (2215 ms)
 - PathChallengeBeforePeerIpAddressChangeAtServer (2284 ms)
 - DetectSimutanuousServerAndClientAddressChangeWithProbe (2358 ms)

All the tests above are parameterized with similar test execution times for the following variants:
 - RFCv2_defer
 - RFCv2_immediate
 - RFCv1_defer
 - RFCv1_immediate
 - draft29_defer
 - draft29_immediate

The DuplicateAckCausesLostPackets test was also slow for the Q046_defer variant.

PiperOrigin-RevId: 650281559