-
Notifications
You must be signed in to change notification settings - Fork 9
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
Coverage is 0 all the time #22
Comments
probably connected with: GoEddie/SQLCover#51 |
@petrce I've got the same issue (or similar) and looking the at Azure DevOps Service Windows Microsoft hosted agent's logs it has to do with creating the extended events trace and suspect it also related to the issue you mentioned I am not sure if it is also because I am using SQL Server 2019 within A VM in azure (but in my sense, it should not make a difference as allow SQL port are open from any client IP connection). See error log and stack trace below running the tSQLt tests and getting Code Coverage... |
I also got same error that of @Gwayaboy . I am running Microsoft SQL Server Enterprise (64-bit) version 13.0.5103.6 . |
Hi, whatever I do coverage stays 0 at Azure SQL any idea how I can debug it?
outside of that task runs flawlessly :)
The text was updated successfully, but these errors were encountered: