[CI] Enable faulthandler to show details when 0xC0000005 error occurs

[hcho3]

From https://xgboost-ci.net/blue/organizations/jenkins/xgboost-win64/detail/release_1.6.0/2/pipeline:

=========================== short test summary info ===========================
SKIPPED [1] tests\python\test_tracker.py:9: Skipping dask tests on Windows
SKIPPED [1] tests\python\test_with_dask.py:28: Skipping dask tests on Windows
SKIPPED [1] tests\python\test_demos.py:160: Test requires sh execution.
SKIPPED [1] tests\python\test_dt.py:21: Datatable is not installed. or Pandas is not installed.
SKIPPED [1] tests\python\test_with_shap.py:16: Requires shap package
========== 277 passed, 5 skipped, 144 warnings in 411.14s (0:06:51) ===========

script returned exit code -1073741819

To show more details, enable the faulthandler in Python (see pytest-dev/pytest#7634).

[hcho3]

@trivialfis Here is the traceback for exit code -1073741819:

 Thread 0x000016e8 (most recent call first):
   File "C:\tools\miniconda3\envs\win64_368556972f29458898d86d03f5f0fbdc\lib\subprocess.py", line 1361 in _wait
   File "C:\tools\miniconda3\envs\win64_368556972f29458898d86d03f5f0fbdc\lib\subprocess.py", line 1083 in wait
   File "C:\tools\miniconda3\envs\win64_368556972f29458898d86d03f5f0fbdc\lib\site-packages\ray\node.py", line 1039 in _kill_process_impl
   File "C:\tools\miniconda3\envs\win64_368556972f29458898d86d03f5f0fbdc\lib\site-packages\ray\node.py", line 983 in _kill_process_type
   File "C:\tools\miniconda3\envs\win64_368556972f29458898d86d03f5f0fbdc\lib\site-packages\ray\node.py", line 1165 in kill_all_processes
   File "C:\tools\miniconda3\envs\win64_368556972f29458898d86d03f5f0fbdc\lib\site-packages\ray\worker.py", line 1031 in shutdown
   File "C:\tools\miniconda3\envs\win64_368556972f29458898d86d03f5f0fbdc\lib\site-packages\ray\_private\client_mode_hook.py", line 105 in wrapper

script returned exit code -1073741819

https://xgboost-ci.net/blue/organizations/jenkins/xgboost-win64/detail/PR-7771/2/pipeline/

[hcho3]

The error is probably coming from Modin. Maybe we should remove it from the Windows pipeline?

[trivialfis]

The error is probably coming from Modin. Maybe we should remove it from the Windows pipeline?

Thank you for investigating this. Sounds good.