Closed rasbt closed 9 months ago
Yeah, I actually intermittently tried pip but then it had some issues with Cython. I wanted to just get it to work again like it used to -- it worked a few months ago. It's really frustrating to not have direct access to the machine and to try it one commit at a time 😅
Willing to take a look/help out. I do ci stuff a lot at work.
Thanks, I think the problem is that we are using old package versions. And there seems to be some incompatibility with the latest Ubuntu version and and old glib version that is required here.
In an ideal world, this could be fixed by updating the unit tests to use the latest packages for pandas etc. But this would require other work in the frequent pattern submodules, which I am saving for a rainy day in the future.
It's tricky. Let's see if this older Ubuntu version works first and go from there 😅
Patch and project coverage have no change.
Comparison is base (
68d4d39
) 77.26% compared to head (a584bb2
) 77.26%. Report is 3 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
It seemed to be a Cython issue that was fixed 🎉 by bumping the sklearn version @jmahlik
I wonder if making a fresh new conda environment might be an alternative to updating the base?
Or pip installing the development requirements in base from a
testing
extra? Likepython -m pip install .[testing]
? Then you might not have to mess with conda updates at all.