[SPARK-46812][PYTHON][TESTS][FOLLOWUP] Check should_test_connect and pyarrow to skip tests #45880
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

What changes were proposed in this pull request?
This is a follow-up of SPARK-46812 to skip the tests more robustly and to recover PyPy CIs.
Why are the changes needed?
should_test_connectcovers more edge cases thanhave_pandas.test_resources.pyhas Arrow usage too.spark/python/pyspark/resource/tests/test_resources.py
Line 85 in 25fc67f
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually tests with
pandasand withoutpyarrow.Was this patch authored or co-authored using generative AI tooling?
No.