forked from golang/tools
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
internal/lsp/regtest: add a benchmark for didChange
Add a benchmark for the processing of workspace/didChange notifications, attempting to isolate the synchronous change processing from asynchronous diagnostics. To enable this, add a new type of expectation that asserts on work that has been _started_, but not necessarily completed. Of course, what we really want to know is whether the current notification has been processed, but that's ~equivalent to knowing whether the next one has been started. Really, it's off-by-one, but amortized over e.g. the 100 iterations of a benchmark we get approximately the right results. Also change some functions to accept testing.TB, because in a first pass at this I modified the regtest framework to operate on testing.B in addition to testing.T... but that didn't work out as IWL is just too slow to execute the benchmarks outside of the environment -- even though we can ResetTimer, the benchmark execution is just too slow to be usable. It seems like a fine change to accept testing.TB is some places, though. For golang/go#45686 Change-Id: I8894444b01177dc947bbed56ec7df80a15a2eae9 Reviewed-on: https://go-review.googlesource.com/c/tools/+/317292 Trust: Robert Findley <[email protected]> Run-TryBot: Robert Findley <[email protected]> gopls-CI: kokoro <[email protected]> TryBot-Result: Go Bot <[email protected]> Reviewed-by: Rebecca Stambler <[email protected]>
- Loading branch information
Showing
9 changed files
with
118 additions
and
37 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters