-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-35721][PYTHON] Path level discover for python unittests #33174
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
Conversation
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #140507 has finished for PR 33174 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #140553 has finished for PR 33174 at commit
|
|
cc @HyukjinKwon @ueshin @viirya @xinrong-databricks |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #140625 has finished for PR 33174 at commit
|
5d1daed to
c6d4f21
Compare
|
Kubernetes integration test unable to build dist. exiting with code: 1 |
|
Test build #140991 has finished for PR 33174 at commit
|
|
Jenkins retest this please. |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #141456 has finished for PR 33174 at commit
|
jenkins also need |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #143721 has finished for PR 33174 at commit
|
|
We're closing this PR because it hasn't been updated in a while. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
What changes were proposed in this pull request?
Add path level discover for python unittests.

Change list:
Note:
pkgutil.walk_packagesandunittest.defaultTestLoader.loadTestsFromModuleto load test modules, consider we will add doctest discover in future, we can add something like blow as the impletations of doctest discover:Why we doesn't add doctests in here? Currently, not all modules doctests are added to
python_test_goals, that means these doctests doesn't be excuted, so better add discover doctests in a separate PR.What's the deps of discover? the test discover will do real import for every modules, so we need install all deps of PySpark test modules before run-tests otherwise the ImportError would be raised.
Why are the changes needed?
Now we need to specify the python test cases by manually when we add a new testcase. Sometime, we forgot to add the testcase to module list, the testcase would not be executed.
Such as:
pyspark-core pyspark.tests.test_pin_thread
Thus we need some auto-discover way to find all testcase rather than specified every case by manually.
related: #32867
Does this PR introduce any user-facing change?
No
How was this patch tested?
Build modules: pyspark-sql, pyspark-mllib, pyspark-resource: https://www.diffchecker.com/4RAQydBB
Build modules: pyspark-core, pyspark-streaming, pyspark-ml: https://www.diffchecker.com/F1ccZDKG
Build modules: pyspark-pandas:https://www.diffchecker.com/eBDne4uA
Build modules: pyspark-pandas-slow:https://www.diffchecker.com/lySQGrhA
./dev/run-tests --parallelism 2 --modules "pyspark-sql"