- 
                Notifications
    You must be signed in to change notification settings 
- Fork 28.9k
SPARK-7021 Add JUnit output for Python unit tests #8323
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
| Jenkins, this is ok to test. | 
| Test build #41290 has finished for   PR 8323 at commit  
 | 
| https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41290/console Can somebody comment on how is Jenkins configured to look for JUnit results (or did this build fail on RAT)? Thanks | 
| The build failed on RAT:  | 
| I just added the headers, xmlrunner is LGPL (and only used to run the tests). | 
| Test build #41291 has finished for   PR 8323 at commit  
 | 
| Is this a no-go because of the license? Thanks | 
| @gliptak Is https://pypi.python.org/pypi/unittest-xml-reporting/1.12.0 an alternative? It is BSD license. We can install the package on Jenkins machines, instead of including the source code in the codebase. | 
| @mengxr Would installing on Jenkins be independent from the codebase (the  | 
| If this new library works, I think we could install it on Spark Jenkins. Could you test it locally and see whether it works? | 
| I tried this locally and the files were generated. Somebody with visibility on Jenkins might need to comment on file locations ... | 
| Test build #42930 has finished for   PR 8323 at commit  
 | 
| Test build #42933 has finished for   PR 8323 at commit  
 | 
| Test build #42935 has finished for   PR 8323 at commit  
 | 
| Please fix Python style issue:  | 
        
          
                python/pyspark/streaming/tests.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.
this should be aligned with tests,. you can run dev/lint-python to check style locally.
| @mengxr Thanks for the local lint pointer | 
| Test build #42980 has finished for   PR 8323 at commit  
 | 
| @shaneknapp Could you take a look at this PR and see whether we can install https://pypi.python.org/pypi/unittest-xml-reporting/1.12.0 on Jenkins? @gliptak We shouldn't make  | 
| could you create a spark issue for the plugin and assign it to me? also, i won't be able to do this until monday, as i'm about to leave town On Thu, Sep 24, 2015 at 2:50 PM, Xiangrui Meng [email protected] 
 | 
| @mengxr Revised. | 
| Test build #42996 has finished for   PR 8323 at commit  
 | 
| @shaneknapp I created https://issues.apache.org/jira/browse/SPARK-10830 and assigned it to you. | 
| test this please | 
| Test build #43015 has finished for   PR 8323 at commit  
 | 
| test this please | 
| unittest-xml-reporting is installed on AMPLab Jenkins. So let's call Jenkins again. | 
| Test build #1821 has finished for   PR 8323 at commit  
 | 
| https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1810/testReport/ doesn't seem to list the Python tests. Can somebody with access to Jenkins configuration review? Thanks | 
| i'll take a look at the config tomorrow On Mon, Sep 28, 2015 at 6:02 PM, gliptak [email protected] wrote: 
 | 
| test this please | 
| Test build #43109 has finished for   PR 8323 at commit  
 | 
| test this please | 
| Test build #43113 has finished for   PR 8323 at commit  
 | 
| @mengxr Thank you for guiding this | 
| test this please | 
| it seems that this PR has a higher-than-normal failure rate .. I don't know why. +@davies | 
| Test build #43176 has finished for   PR 8323 at commit  
 | 
| test this please | 
| Test build #43252 has finished for   PR 8323 at commit  
 | 
| Huh, looks like the last two failures were for the same PySpark test:  | 
| I guess that this doesn't handle doctests, right? Is there any way to get XML for those, too? If not, could you edit the PR title / description to reflect this? | 
| @gliptak, can you try to reproduce the failure locally? See  | 
| @JoshRosen I do not have python2.6 installed (or available as a package) locally | 
| @JoshRosen How are the doctest-s triggered on the commandline and in Jenkins?  | 
| What is the next step on this pull request? Thanks | 
| @gliptak I had an offline discussion with @davies . Let's do the following: 
 Then we can run Jenkins again and see whether it works. | 
| Test build #43863 has finished for   PR 8323 at commit  
 | 
| Right now, all the Python unit tests are in the package of  | 
| @davies Not that I see. I opened xmlrunner/unittest-xml-reporting#95 to discuss. | 
| @JoshRosen I opened xmlrunner/unittest-xml-reporting#94 to discuss doctests processing. | 
| This looks good to me. I think we can address the test namespace issue in a later PR. @davies @JoshRosen ? | 
| LGTM, merging this into master, thanks! | 
| As per xmlrunner/unittest-xml-reporting#95 the Python tests do not have packages (or possibly not being recognized by https://github.com/xmlrunner/unittest-xml-reporting/ | 
| Adding packages to XMLs at #9263 | 
WIP