When updating our inExperiment method to call non-deprecated ExP methods in #16486, this caused some seemingly unrelated tests to fail. Some changes fixed most of the test failures, except for the Windows venv tests (see this run):
1) Activation of Environments in Terminal
"before each" hook for "Should activate with venv":
Error: Timeout of 25000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (d:\a\vscode-python\vscode-python\path with spaces\out\test\common\terminals\environmentActivationProviders\terminalActivation.testvirtualenvs.js)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
2) Activation of Environments in Terminal
"after all" hook for "Should activate with conda":
Error: Timeout of 50000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (d:\a\vscode-python\vscode-python\path with spaces\out\test\common\terminals\environmentActivationProviders\terminalActivation.testvirtualenvs.js)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
3) WorkspaceVirtualEnvironment Locator
Detect a new environment:
Error: Timeout of 25000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (d:\a\vscode-python\vscode-python\path with spaces\out\test\pythonEnvironments\base\locators\lowLevel\workspaceVirtualEnvLocator.testvirtualenvs.js)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
When updating our
inExperimentmethod to call non-deprecated ExP methods in #16486, this caused some seemingly unrelated tests to fail. Some changes fixed most of the test failures, except for the Windows venv tests (see this run):