Right now we have 2 failing tests which pop up from time to time (here both are triggered):

1. on Linux - client_deglob (previously test_deglob)

Processing message: Object({"id": Number(1100), "jsonrpc": String("2.0"), "result": Array([])})
thread 'client_deglob' panicked at 'called `Option::unwrap()` on a `None` value', src/libcore/option.rs:345:21

We sometimes don't get a response for the second deglob requests for a line with 2 glob imports

2. on Windows - client_use_statement_completion_doesnt_suggest_arguments

Processing message: Object({"id": Number(100), "jsonrpc": String("2.0"), "result": Array([])})
thread 'client_use_statement_completion_doesnt_suggest_arguments' panicked at 'Racer autocompletion failed', src\libcore\option.rs:1038:5

Sometimes Racer autocompletion returns empty (which is weird, given we're already waiting till the project is indexed and we wait for Racer to perform its analysis) results.

It's important we tackle this issue since

• in the past these sometimes spuriously failed in the Rust repo, flagging RLS as broken (which it wasn't)
• about a third of our CI checks fail because of these