Large subtest qty freezes some UI elements #21339
Assignees
Labels
Comments
github-actions
bot
added
the
triage-needed
|
1st run = success |
|
What I think is happening is it is sending a test_id per subtest but all the subtests have the same test_id. Therefore if there are 100 subtests, it is running 100 subtests, 100 times since it is running the subtest parent 100 times. This will be fixed if only unique test_ids are passed into the run command so then it will run the list of subtests only a single time. Here is a display of the logs, you can see it runs a single test first then attempts to run 100. |
github-actions
bot
added
the
info-needed
eleanorjboyd
added a commit
that referenced
this issue
May 31, 2023
this will partially remediate #21339 in regards to the duplicate IDs being run.
eleanorjboyd
added
bug
eleanorjboyd
added a commit
that referenced
this issue
Jun 5, 2023
follows the same steps as making pytest compatible with large workspaces with many tests. Now test_ids are sent over a port as a json instead of in the exec function which can hit a cap on # of characters. Should fix #21339.
eleanorjboyd
added a commit
to eleanorjboyd/vscode-python
that referenced
this issue
Jun 5, 2023
follows the same steps as making pytest compatible with large workspaces with many tests. Now test_ids are sent over a port as a json instead of in the exec function which can hit a cap on # of characters. Should fix microsoft#21339.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Testing #21306
subtest with
range (0, 10k)caused a number of UI elements to freeze while running, most apparent when resizing the window.*note: all actions resolve and render properly immediately upon test completion
While the 10k subtests are running, the window cannot be closed nor reloaded. UI elements can be interacted with, but nothing happens other than visually showing that they were clicked upon.
ex: folders showing as expanded, but not showing contents
other graphical issues
The text was updated successfully, but these errors were encountered: