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

Revisit behavior and clarify documentation around SourceNamespace #13

Open
isc-tleavitt opened this issue Mar 31, 2022 · 1 comment
Open
Assignees
Labels
bug Something isn't working

Comments

@isc-tleavitt
Copy link
Collaborator

This turned out to be the root cause behind https://community.intersystems.com/post/errors-when-using-testcoverage-error-5002-objectscript-error . It would be nice if we didn't need SourceNamespace and everything could "just work" regardless of where the code lives. Alternatively, if it's needed, we should provide a more descriptive error message.

Should also investigate behavior of saving results when SourceNamespace is used, as this seemed off.

@isc-tleavitt
Copy link
Collaborator Author

Actually seems like the issue was related to having bad things cached; running ##class(TestCoverage.Utils).Clear() fixed the issue.
I think we should always treat the cache as invalid if ExecutableLines shows nothing could be run.

@isc-tleavitt isc-tleavitt added the bug Something isn't working label Nov 30, 2023
@isc-tleavitt isc-tleavitt self-assigned this Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant