You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems to be caused by our use of symlinking for the examples directory. When I run the tests locally, the initial coverage report correctly gets the examples. But if I generate an html report (with coverage html) then the examples directory is omitted completely.
Coveralls is including the examples directory but reporting as if we didn't run any of it. This causes overall coverage to be drastically underreported.
One option would be to just move the examples directory down into pyclaw/src/pyclaw/. Or to move everything else up into clawpack/pyclaw.
The text was updated successfully, but these errors were encountered:
Sorry, I was on my mobile all yesterday. I am just trying to understand what you mean by your options above, namely what context would are you suggesting moving the examples directory. I have not really dealt much with cover-alls so that might be part of the problem.
I am suggesting revising the directory structure so that coveralls can correctly detect our test coverage. I think that less tricky symlinking would be beneficial anyway.
This seems to be caused by our use of symlinking for the examples directory. When I run the tests locally, the initial coverage report correctly gets the examples. But if I generate an html report (with
coverage html
) then the examples directory is omitted completely.Coveralls is including the examples directory but reporting as if we didn't run any of it. This causes overall coverage to be drastically underreported.
One option would be to just move the examples directory down into pyclaw/src/pyclaw/. Or to move everything else up into clawpack/pyclaw.
The text was updated successfully, but these errors were encountered: