This repository was archived by the owner on Dec 29, 2022. It is now read-only.
Ci testing: Retry completions on empty response #1099
Merged
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.
We're still not fully reliable in CI, in particular the "cmd_" tests. This change adds completion request retrying if we get back empty results to work around a race for rls to be ready to return the completions. It also adds a pattern of waiting on response-id rather than expectation, which should reduce the chances of timeout in favour of fast-failing.
Ci failure
From the std out we can see
{"jsonrpc":"2.0","id":0,"result":[]}
at the end which is not what the test expects. As this happens only sometimes in CI, we can assume there is a race condition & rls is not always ready to respond to a completion request immediately after sending indexing-done.This change assumes rls would eventually return the correct completion on retry so: