-
Notifications
You must be signed in to change notification settings - Fork 28.9k
SPARK-11741 Process doctests using TextTestRunner/XMLTestRunner #9710
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
|
#8323 |
|
Test build #45910 has finished for PR 9710 at commit
|
|
Working to improve tooling at xmlrunner/unittest-xml-reporting#100 |
|
@davies @mengxr @JoshRosen Please review. Thanks |
|
@JoshRosen Please review. |
|
Same comment as on your other PR: can you please write a PR description for this which explains the change and summarizes what you did? Also, what's the status of the |
|
xmlrunner/unittest-xml-reporting#100 was committed but not yet released. The version 1.12.0 installed with https://issues.apache.org/jira/browse/SPARK-10830 works, we could update to 1.14.0 (when released). |
|
Will the code here need to update after a new version of that library is released or will we only have to bump in Jenkins? If we won't have to do any code changes, then I think we should go ahead and modify the other files to also use this code. Since the few lines of test runner configuration might be duplicated in a bunch of files, we could refactor them into a separate function which we call in each file. |
|
I'm only foreseeing a library version bump. |
|
Okay, sounds good. Do you want to go ahead and apply this change to the other PySpark files? |
|
Test build #49432 has finished for PR 9710 at commit
|
|
Test build #49512 has finished for PR 9710 at commit
|
|
@mengxr Locally I see a number of these doctests fail. Should failing ones be commented and JIRAs opened against them? Thanks |
What is the recommended way to tag this class private? |
|
Test build #49536 has finished for PR 9710 at commit
|
|
Upthread, I suggested taking the code which handles the xmlrunner imports and configuration and putting it into a reusable function which is defined in one place and called in the |
|
@JoshRosen Please review accumulators.py |
python/pyspark/doctesthelper.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before merging, we're going to want to remove this print statement I think.
|
Those changes to |
|
Test build #49965 has finished for PR 9710 at commit
|
|
Test build #50045 has finished for PR 9710 at commit
|
|
@JoshRosen A number of the doctests do fail locally too. I'm also unsure why only a single test result shows ... |
|
@JoshRosen Could you offer ointers on how to move this forward? Thanks |
|
Rebased. |
|
Test build #51137 has finished for PR 9710 at commit
|
|
Test build #51149 has finished for PR 9710 at commit
|
|
Test build #51158 has finished for PR 9710 at commit
|
|
@JoshRosen Could you offer pointers on how to move this forward? Thanks |
|
@JoshRosen Are you still considering this for inclusion? Thanks |
|
Test build #53638 has finished for PR 9710 at commit
|
SPARK-11741 Process doctests using TextTestRunner/XMLTestRunner
Doctests were moved under a class to correct processing