Closed TCLiuu closed 8 months ago
Should we remove TestParticleMakie
from registry?
Attention: 1 lines
in your changes are missing coverage. Please review.
Comparison is base (
c6a615c
) 63.73% compared to head (b247145
) 70.94%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
There is still an issue. Should we merge the testCI of TestParticlemakie and TestParticle? If not, the coverage report will have some strange problems when the testCI of TestParticlemakie does not run, as it occurred in those PRs before.
Should we remove
TestParticleMakie
from registry?
If I remember correctly, there is currently no way of removing a package from the registry. We can simply mark it as archived and leave it there.
There is still an issue. Should we merge the testCI of TestParticlemakie and TestParticle? If not, the coverage report will have some strange problems when the testCI of TestParticlemakie does not run, as it occurred in those PRs before.
I think we should merge the visual tests into the main tests. With CairoMakie and the CI cache system, this should not add too much test time. See an example here. They list CairoMakie as a test Project.toml dependency and always import it. I saw your approach of checking args in runtest.jl. This is also good.
This is almost done! Nice job!