-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spurious RLS test failures #62225
Comments
The tracking issue is in rust-lang/rls#1265. |
#62209 (comment) also seems spurious. |
Indeed, and it's an interesting one: So this bug has already caused two PRs to fail to land within the last 24h. |
Merged RLS test fixes:
Failed because it's a stable backport, which doesn't yet include #61694
Double-checked and every failure is prior to merging #61861 ...which means that the only spurious test failure in the past 10 days is #61199 (comment) (the other two instances of It looks like |
@Xanewok thanks for the update, good to hear that Do you have any inkling as to what might cause these failures? |
I have a hunch that we might have a race in Racer (heh) + RLS in About |
FWIW, this seems to be still happening: |
Closing as #100863 has removed RLS. |
The RLS tests regularly fail on the tools builder even when the PR didn't touch anything RLS-related, and then the next PR landing switches the toolstate back to test-pass again. This is particularly bad during the week before the beta cutoff, where such a test failure leads to the PR being rejected.
I have seen this for weeks or even months, but to my surprise could not find an issue tracking this yet.
Cc @rust-lang/infra @Xanewok
Some examples (with failing platform and test):
#62209 (comment) (Linux, client_changing_workspace_lib_retains_diagnostics)
#61199 (comment) (Linux, client_find_definitions)
#61891 (comment) (Windows, client_completion_suggests_arguments_in_statements)
#61932 (comment) (Linux, client_completion_suggests_arguments_in_statements)
#61771 (comment) (Linux, client_completion_suggests_arguments_in_statements)
#61889 (comment) (Windows, client_completion_suggests_arguments_in_statements)
#60730 (comment) (Windows, client_completion_suggests_arguments_in_statements)
#59752 (comment) (Linux, client_completion_suggests_arguments_in_statements)
#61817 (comment) (Linux, client_find_definitions)
#61789 (comment) (Linux, client_completion_suggests_arguments_in_statements)
#61722 (comment) (Linux, client_completion_suggests_arguments_in_statements)
#61758 (comment) (Linux, client_find_definitions)
And that's just for the last 17 days!
The text was updated successfully, but these errors were encountered: