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

handle un-analyzable files in coverage run #24800

Merged
merged 2 commits into from
Feb 7, 2025

Conversation

eleanorjboyd
Copy link
Member

fixes #24703

@eleanorjboyd eleanorjboyd added the bug Issue identified by VS Code Team member as probable bug label Feb 7, 2025
@eleanorjboyd eleanorjboyd added this to the February 2025 milestone Feb 7, 2025
@eleanorjboyd eleanorjboyd self-assigned this Feb 7, 2025
Copy link

⚠️ This PR originates from a fork. Due to security restrictions, pipelines from forks are no longer triggered automatically. Learn more.

If the changes appear safe, you can manually trigger the pipeline by commenting /AzurePipelines run.

@eleanorjboyd eleanorjboyd enabled auto-merge (squash) February 7, 2025 22:20
@eleanorjboyd eleanorjboyd merged commit b4aa112 into microsoft:main Feb 7, 2025
46 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pytest code coverage run fails after attempting to parse non-Python file
2 participants