-
Notifications
You must be signed in to change notification settings - Fork 11
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
testing issues #66
Comments
I think this may be an issue with current version of |
I installed chardet, and it put in the latest version (5.2.0), but this does not solve the problem. I see you use the ray package. I have not looked too deeply into it, but it could even be a bug there. Do all your tests pass? |
At my end (Windows 10 and Windows 11), all tests pass, but did initially encounter a similar error. I will try to reproduce the error in a fresh environment, and figure out which package I installed to resolve it. That package may need to be listed as a dependency. |
I was not able to reproduce the issue. My environment is as follows. Note that I installed
|
Tests on multiple platforms were not able to reproduce the error, see #70. |
I cannot reproduce the issue on my Windows installation. The issue is likely with
I have added an try-except block to capture OS errors that prevent ray instances from being to created. A warning is shown instead. |
On my machine there are a couple of failing tests:
FAILED test/parallel_feature_extraction_test.py::test_parallel_feature_extraction - OSError: [Errno 0] AssignProcessToJobObject() failed
FAILED test/parallel_feature_extraction_test.py::test_parallel_dl_preprocessing - OSError: [Errno 0] AssignProcessToJobObject() failed
If these don't fail for you, I can look into it, and with permission given the requirements of the JOSS process, maybe even put in a PR (but I'm not sure if this is allowed)
The text was updated successfully, but these errors were encountered: