Fixes flaky serverless reporting tests #244993
Open
+1
−0
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.
Fixes #237285
Summary
The serverless version of these tests were failing with
Response aborted while reading the bodyerrors, which means the report is short-circuiting before completing. I noticed a previous change #185878 to increase the time the test waits for a report to10mhowever, the queue timeout for reporting was still set to the default4mso this increases the queue timeout for reporting to10min these tests to give it more time to complete.This should also address the following tests (all failed due to
Response aborted while reading the body):Flaky test runner runs:
There were some failures but seem unrelated...