Attempt to dodge flakiness in heavy_tasks_doesnt_block_graphql
test
#2437
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.
Closes #2435
Description
This is an attempt to resolve observed flakiness in the
heavy_tasks_doesnt_block_graphql
test.When I tested the fix locally, with much smaller (250ms) timeouts and debug prints, I could observe the following outcome:
Changes:
3. Reduce timeout from 5 to 4 seconds
4. Spam the node with 3 times as much requests in the background (50 -> 150).
This is an effort to make the test more resilient to the performance of the machine it is executed on.
Before requesting review