-
Notifications
You must be signed in to change notification settings - Fork 234
Improve CI stability #1848
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
Improve CI stability #1848
Conversation
@@ -109,6 +111,7 @@ public async Task CompletesVariableInFile() | |||
public async Task CompletesAttributeValue() | |||
{ | |||
(_, IEnumerable<CompletionItem> results) = await GetCompletionResultsAsync(CompleteAttributeValue.SourceDetails).ConfigureAwait(true); | |||
Assert.Equal(3, results.Count()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this fails in flaky test, we'll know that it's not a sorting issue (which it shouldn't be, because we already sort it, but this has been hell to figure out).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Well done getting this figured out ❤️ looking forward to not having to restart so many test runs 😁
7d166b5
to
d8e76d2
Compare
Our CI can be quite slow, and these were just arbitrary timeouts. If the tests succeed, they should never be hit. Let's instead give them as much time as possible. CI will eventually kill the run if it hangs, and locally devs can do the same. This should help improve CI stability. Also fixes the disposal bug in the tests.
d8e76d2
to
7eefe68
Compare
7eefe68
to
80ab5a4
Compare
By removing arbitrary timeouts, fixing disposal bugs, and cleaning up tests. Resolves #1793.