Skip to content
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

Discovering tests immediately after interpreter change often fails #9854

Closed
karrtikr opened this issue Jan 31, 2020 · 0 comments · Fixed by #16769
Closed

Discovering tests immediately after interpreter change often fails #9854

karrtikr opened this issue Jan 31, 2020 · 0 comments · Fixed by #16769
Labels
area-testing bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@karrtikr
Copy link

While solving #9614, we added a hook that on interpreter change, we call the API to auto discover the tests.
But that's eventually returning without discovering the tests as test manager is not ready to discover tests immediately on interpreter change for some reason.

Adding a delay before calling the API should probably solve the issue.

@karrtikr karrtikr added bug Issue identified by VS Code Team member as probable bug needs PR area-testing labels Jan 31, 2020
@karthiknadig karthiknadig added the verification-found Issue verification failed label Jul 29, 2021
@brettcannon brettcannon added verified Verification succeeded and removed verification-found Issue verification failed labels Aug 3, 2021
@karthiknadig karthiknadig added this to the August 2021 milestone Aug 5, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-testing bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants