Skip to content

Conversation

@cocolato
Copy link
Collaborator

@cocolato cocolato commented Apr 18, 2024

Fix: #260

@cocolato
Copy link
Collaborator Author

Maybe 3.6 testing should be skipped. I'm not sure if this implementation is what we want.

@aisk
Copy link
Member

aisk commented Apr 24, 2024

I think this approach is fine for me. But there are some tests that have been skipped because they require fork to start multiprocessing. So with this change, if this approach can solve the problem, we should enable these skipped tests to ensure that this change works as we expected.

For skipping the test on Windows with Python 3.6, I think maybe multiprocess does not support some functionalities on Windows with Python 3.6. So I'm fine with skipping it, but since it passed on Linux, I think we can modify the build.yaml to have it only skip on Windows with Python 3.6.

@cocolato cocolato marked this pull request as draft July 15, 2024 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Get rid of using fork start method for mp module in the tests

2 participants