We should stay away from logging to tests, esp. when we now have to find leak messages:
ModelSemanticColoring
✔ DocumentSemanticTokens should be fetched when the result is empty if there are pending changes
[66705:0907/173526.520437:INFO:CONSOLE(119)] "Invalid semantic tokens edit detected (previousResultId: 1, resultId: 2) at edit #0: The provided start offset 4294967276 is outside the previous data (length 10).", source: file:///Users/bpasero/Development/Microsoft/vscode/out/vs/editor/common/services/semanticTokensProviderStyling.js (119)
✔ issue #149412: VS Code hangs when bad semantic token data is received
✔ issue #161573: onDidChangeSemanticTokens doesn't consistently trigger provideDocumentSemanticTokens
✔ DocumentSemanticTokens should be pick the token provider with actual items
ModelService
[66705:0907/173537.842613:INFO:CONSOLE(107)] "Overlapping semantic tokens detected at lineNumber 3, column 37", source: file:///Users/bpasero/Development/Microsoft/vscode/out/vs/editor/common/services/semanticTokensProviderStyling.js (107)
✔ issue #134973: invalid semantic tokens should be handled better
[66705:0907/173537.848274:INFO:CONSOLE(113)] "Semantic token with invalid length detected at lineNumber 1, column 16", source: file:///Users/bpasero/Development/Microsoft/vscode/out/vs/editor/common/services/semanticTokensProviderStyling.js (113)
[66705:0907/173537.848318:INFO:CONSOLE(107)] "Overlapping semantic tokens detected at lineNumber 1, column 10", source: file:///Users/bpasero/Development/Microsoft/vscode/out/vs/editor/common/services/semanticTokensProviderStyling.js (107)
✔ issue #148651: VSCode UI process can hang if a semantic token with negative values is returned by language service
[66705:0907/173537.853718:INFO:CONSOLE(107)] "Overlapping semantic tokens detected at lineNumber 1, column 9", source: file:///Users/bpasero/Development/Microsoft/vscode/out/vs/editor/common/services/semanticTokensProviderStyling.js (107)
✔ issue #149130: vscode freezes because of Bracket Pair Colorization
We should stay away from logging to tests, esp. when we now have to find leak messages: