Improve GraphQL analyzer timeout handling
What does this MR do and why?
In the last iteration,
!154466 (merged), we made
sure that there would be data present in case of an error. But this
resulted in an error object getting saved into results[:complexity],
which makes it harder than necessary to identify logs with timeout
errors. For example, in our ElasticSearch instance, this causes the
complexity to get ignored.
See #462387 (closed)
For some examples, see our production logs (internal link).
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Run the new test with and without my code changes.
Edited by Hordur Freyr Yngvason