Skip flaky vscode test suites #23535
Merged
Conversation
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
|
The unit test failure appears related to xtermjs/xterm.js#4560. It's still not clear to me if there is a limited subset of suites that are hitting this issue, or if it can show up somewhat randomly across the suites. |
|
Let's take this for now and I'll keep the tracking issue open. If the canary builds don't get stabilized I'll revert and try a different approach. |
cssuh
pushed a commit
that referenced
this pull request
Jun 30, 2023
* Skip flaky vscode test suites * One more upstream test that's failed intermittently in recent CI * One more suite * Another suite
lewis-sanchez
added a commit
that referenced
this pull request
Jul 11, 2023
This reverts commit 882bdb3.
lewis-sanchez
added a commit
that referenced
this pull request
Jul 11, 2023
* Makes use of xvfb to run unit tests * Restore test script as before, but with xvfb * Use same command that worked in CLI * Add --build CLI arg * Add coverage arg * Revert change to core unit test script * Reset core unit tests script in linux pipeline * Revert "Skip flaky vscode test suites (#23535)" This reverts commit 882bdb3. * Revert "Disable failing vscode test suite (#23539)" This reverts commit 562a0ce. * Revert "Disable vscode remote configuration suite (#23545)" This reverts commit 40fa1ce. * Revert "Disable editor resolver service test suite (#23550)" This reverts commit cd68dca. * Revert "Disable upstream extension enablement suite (#23557)" This reverts commit faf3c69. * Revert "Skip a few more suites impacted by xterm issue (#23589)" This reverts commit 1662ced. # Conflicts: # src/vs/workbench/contrib/experiments/test/electron-sandbox/experimentService.test.ts * Use DOM Renderer for tests * Remove extra whitespace * Update comment
lewis-sanchez
added a commit
that referenced
this pull request
Jul 11, 2023
* Makes use of xvfb to run unit tests * Restore test script as before, but with xvfb * Use same command that worked in CLI * Add --build CLI arg * Add coverage arg * Revert change to core unit test script * Reset core unit tests script in linux pipeline * Revert "Skip flaky vscode test suites (#23535)" This reverts commit 882bdb3. * Revert "Disable failing vscode test suite (#23539)" This reverts commit 562a0ce. * Revert "Disable vscode remote configuration suite (#23545)" This reverts commit 40fa1ce. * Revert "Disable editor resolver service test suite (#23550)" This reverts commit cd68dca. * Revert "Disable upstream extension enablement suite (#23557)" This reverts commit faf3c69. * Revert "Skip a few more suites impacted by xterm issue (#23589)" This reverts commit 1662ced. # Conflicts: # src/vs/workbench/contrib/experiments/test/electron-sandbox/experimentService.test.ts * Use DOM Renderer for tests * Remove extra whitespace * Update comment
kisantia
pushed a commit
that referenced
this pull request
Jul 11, 2023
* Makes use of xvfb to run unit tests * Restore test script as before, but with xvfb * Use same command that worked in CLI * Add --build CLI arg * Add coverage arg * Revert change to core unit test script * Reset core unit tests script in linux pipeline * Revert "Skip flaky vscode test suites (#23535)" This reverts commit 882bdb3. * Revert "Disable failing vscode test suite (#23539)" This reverts commit 562a0ce. * Revert "Disable vscode remote configuration suite (#23545)" This reverts commit 40fa1ce. * Revert "Disable editor resolver service test suite (#23550)" This reverts commit cd68dca. * Revert "Disable upstream extension enablement suite (#23557)" This reverts commit faf3c69. * Revert "Skip a few more suites impacted by xterm issue (#23589)" This reverts commit 1662ced. # Conflicts: # src/vs/workbench/contrib/experiments/test/electron-sandbox/experimentService.test.ts * Use DOM Renderer for tests * Remove extra whitespace * Update comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These suites are intermittently being impacted by the xterm glyph issue. The actual upstream product functionality seems to be working fine, so it seems safe to disable in our test runs since we don't routinely modify these product areas.