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
check_regressors_train failure on master with the latest release on conda #14106
Comments
@adrinjalali Should we try to resolve this before the sprint? |
It'd be nice, since it may confuse people there. |
@glemaitre I can't really reproduce this, could you please give us maybe a reproducing code? |
It is weird. It does not happen anymore, maybe an Heisenbug. For instance, for this build: |
We should rather check the precise versions of packages being loaded from conda during and after the failure, to identify if some combination of versions results in the issue. |
There is no diff in the versions used in the erroring build and the current build. |
Uhm I checked the common test and I think that Ransac was tagged as |
Reopening since this is still happening time to time |
Closing since this was fixed in #21781 and all related PRs. Also the memmap issue was fixed on the joblib side here: joblib/joblib#1254 |
Note that joblib has not be released yet at the time of writing but it should happen soon-ish. |
We spot a failure of
check_regressors_train
(with X being an array or a memmap) on master.The failure happened for:
We should investigate this issue.
The text was updated successfully, but these errors were encountered: