Closed veni-vidi-vici-dormivi closed 1 month ago
It currently fails because there is no mesmer.geospatial
module (which is true, the stuff is in mesmer.core.geospatial
so it needs import mesmer
and we need to call mesmer.spatial.calc_geodist_exact(...)
. Sorry about that.
I want to exclude two files from the tests, I guess I should edit the pre commit config in another PR?
You want to remove them from running via pytest? I think that should be possible here. But it might be best to get it to run locally, as these import conflicts can be quite annoying...
so it needs import mesmer and we need to call mesmer.spatial.calc_geodist_exact(...).
Why can't we use mesmer.core.geospatial.geodist_exact()
?
But it might be best to get it to run locally, as these import conflicts can be quite annoying...
So it fails because OLD_train_l_distrib.py
and create_emus_l_dristrib.py
use functions from a mesmer.utils that does not exist anymore. I talked with Yann about this in #438, and it is because these two are old files which should be replaced by the other/new files. This is why I think it makes sense to exclude them from any testing.
I think the fix now is to move example_mesmer_x.py to the example folder (or to wrap the code in the file to if __name__ == "__main__"
block, but the example code should not live in the mesmer code folder).
Attention: Patch coverage is 0%
with 190 lines
in your changes are missing coverage. Please review.
Please upload report for BASE (
mesmer_x@dce593b
). Learn more about missing BASE report.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Love your commit names ;-) At the risk of making myself very unpopular - I prefer the comments above the code (but ok to leave it like that if it's too stupid for you)
I prefer the comments above the code (but ok to leave it like that if it's too stupid for you)
Well that actually makes two of us... I'm switching to a more entertaining Spotify playlist for that one...
Now you are just showing off 😉
Okay this is ready imo.
Is there no branch protection on this one? I dont see that I need a review...
Probably because you don't want to merge into main. I am looking at the code now.
could you have a quick look at the workaround in the example? 🙏 @mathause
Yes ok for me. Could also use # noqa: F841
(needs to be on the line the variable is defined, i.e.
a = ( # noqa: F841
5,
6,
)
)
Ah I like that a little better thanks!
Close/ reopen to trigger another rtd build
It's still failing, but they don't give any information as to why?
🎉
I want to exclude two files from the tests, I guess I should edit the pre commit config in another PR?