-
Notifications
You must be signed in to change notification settings - Fork 906
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
Investigate flaky unit tests failing intermittently after vscode source refresh #23509
Comments
I've tried to disable the suites I'm seeing failing in the canary builds to understand if this xterm issue is isolated to a handful suites, and to try to stabilize the canary & PR builds. #23535. This doesn't seem like a good long-term fix so will continue to investigate after looking at some other issues. |
This PR disables an additional suite for the same issue #23539. |
This is one more suite impacted by this issue #23545. |
One more test suite #23550. |
One more #23557 |
The xterm glyph issue keeps popping up during other suites, so I'm going to stop disabling them. Though I will keep the above mentioned one disabled while investigating the builds are significantly more stable w/o them. |
Additional suites that failed in canary yesterday #23589 |
A few more tests with similar error:
|
I chatted with Daniel from the VS Code team (owns the xterm stuff there) and his suggestion for a temporary fix would be to set up the tests to use the DOM renderer instead like they do for their smoke tests : https://github.com/microsoft/vscode/blob/0c3fb42a1e31f63ec7f17906a19bbcebdbe8bb3e/test/smoke/src/areas/terminal/terminal-helpers.ts#L15-L17 I'll try to send out for a PR for that this week, but if anyone else had time feel free to take this up 😄 |
There have still been test failures in the canary builds after #23770 was merged. @lewis-sanchez can you please take another look and disable these if needed?
|
Before disabling, please see if these tests are using the config that you added in the previous PR. If that test config service isn't actually used by every test by default then we may need to find another solution to ensure that every test picks up the config. If it is being used then we should probably revert the change - since it doesn't seem to actually solve the problem - and investigate other options (such as fixing xterm itself). |
There are a handful of unit tests failing intermittently in the canary builds that need to be investigated. I'll use this issue to keep a list of these tests and provide status on fixing, disabling, etc.
Initial list of tests to investigate:
The text was updated successfully, but these errors were encountered: