Enable bulking test on windows#14392
Conversation
|
@mxnet-label-bot add [CI, Test, Windows, pr-work-in-progress]] |
|
If this latest commit passes CI, it will be ready for merging. The problem is that when one performs in Python: this effects what the C++ backend sees only on Linux. Under Windows, some additional (and possibly windows-version-specific) work would be required to push the environment change to the msvcrt, which otherwise gets a copy of the environment at process start-up. My preferred fix here is to resort to the more bomb-proof approach of setting environment variables, then spawning a new process to perform the test (although admittedly this is bypassed on Python2 due to lack of spawn support). |
|
Ready for your review. @perdasilva @eric-haibin-lin @szha |
* Reenable test_operator_gpu.py:test_bulking. * Add temporary debug output. * Add test_gluon_gpu.py:test_bulking to test spawn approach. * Reorder testing to see test_gluon_gpu.py:test_bulking result. * Change test_operator_gpu.py:test_bulking to use spawn approach. * Remove diagnostic output and revert windows ci changes.
* Reenable test_operator_gpu.py:test_bulking. * Add temporary debug output. * Add test_gluon_gpu.py:test_bulking to test spawn approach. * Reorder testing to see test_gluon_gpu.py:test_bulking result. * Change test_operator_gpu.py:test_bulking to use spawn approach. * Remove diagnostic output and revert windows ci changes.
* Reenable test_operator_gpu.py:test_bulking. * Add temporary debug output. * Add test_gluon_gpu.py:test_bulking to test spawn approach. * Reorder testing to see test_gluon_gpu.py:test_bulking result. * Change test_operator_gpu.py:test_bulking to use spawn approach. * Remove diagnostic output and revert windows ci changes.
Description
This PR is a response to #14368 and is now ready for merging. The first step here was to recreate the Windows CI failure, along with additional debugging output to show whether the intended bulking environment variable settings were making it to the point of use. I learned that the test's repeated setting and altering of environment variables was not getting through to the C++ runtime under Windows, which apparently gets a copy of the environment at process start-up. The fix was to spawn a new test process for each setting of different environment variables, as is already done for the gluon version of these same tests.
Thanks to @perdasilva for identifying this issue.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.
Changes
Comments