bpo-31904: Fix test_os failures for VxWorks RTOS by yuesun1 · Pull Request #12319 · python/cpython (original) (raw)
This is the successive PR after #11968 and #12118. The resource.setrlimit() can't set NOFILE to 1 on VxWorks, we can only track the highest fd value in use, and only permit lowering NOFILE up to that value, so in testcase 'test_urandom_failure' I have to keep opening '/dev/null' until reporting errno EMFILE to make sure the fd table is full already and we can't open any more file.
And the VxWorks doesn't support execv like functions, so I skipped them.
More and full support on modules for VxWorks will continuously be added by the coming PRs.
VxWorks is a product developed and owned by Wind River. For VxWorks introduction or more details, go to https://www.windriver.com/products/vxworks/
Wind River will have a dedicated engineering team to contribute to the support as maintainers.
We already have a working buildbot worker internally, but has not bound to master. We will check the process for the buildbot, then add it.