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
test_uuid.py and test_ssl.py failure on OSes without os.fork (VxWorks RTOS) #85611
Comments
Some operating systems, for example VxWorks RTOS, don't support fork(). Some test cases that depend on os.fork() will fail. |
Are this and similar issues theoretical ("if Python were implemented on such systems...") or actual ("python is implemented on one such system (VxWorks?) and these tests fail"). If the latter, does the test suite pass at least with respect to, in this case, os.fork? I expect that there are other tests that depend on os.fork, but maybe they are already guarded. |
Similar issues: PR 21684 is fine as far as it goes, and I could merge and backport, but I don't know about our test policy with respect to need and minimized OSes. We do not put conditions for unsupported oses in production code, but I don't know about skips for such systems in tests. Victor, do you know, or know who would? |
Terry, VxWorks has not been officially supported by community. Certainly no builtbot for VxWorks connected yet. I am porting cpython onto VxWorks RTOS now. Several issues you listed are the part of my porting effort. So I think we don't need to backport the fix to previous versions. |
Thanks Peixing Xin, I merged your fix. Terry:
I don't think that it's worth it to backport to 3.9: Python 3.9 doesn't support VxWorks. I prefer to only merge VxWorks changes in the master branch. Terry:
The final change is not specific to VxWorks and so reasonable. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: