Uh oh!
There was an error while loading. Please reload this page.
SPARK-7021 Add JUnit output for Python unit tests - #8323
Conversation
JoshRosen
commented
Aug 19, 2015
Jenkins, this is ok to test. |
SparkQA
commented
Aug 19, 2015
Test build #41290 has finished for PR 8323 at commit
|
gliptak
commented
Aug 19, 2015
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 |
JoshRosen
commented
Aug 19, 2015
The build failed on RAT: |
gliptak
commented
Aug 19, 2015
I just added the headers, xmlrunner is LGPL (and only used to run the tests). |
SparkQA
commented
Aug 19, 2015
Test build #41291 has finished for PR 8323 at commit
|
gliptak
commented
Aug 20, 2015
Is this a no-go because of the license? Thanks |
mengxr
commented
Sep 22, 2015
@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. |
gliptak
commented
Sep 23, 2015
@mengxr Would installing on Jenkins be independent from the codebase (the |
mengxr
commented
Sep 23, 2015
If this new library works, I think we could install it on Spark Jenkins. Could you test it locally and see whether it works? |
gliptak
commented
Sep 23, 2015
I tried this locally and the files were generated. Somebody with visibility on Jenkins might need to comment on file locations ... |
SparkQA
commented
Sep 23, 2015
Test build #42930 has finished for PR 8323 at commit
|
SparkQA
commented
Sep 23, 2015
Test build #42933 has finished for PR 8323 at commit
|
SparkQA
commented
Sep 23, 2015
Test build #42935 has finished for PR 8323 at commit
|
mengxr
commented
Sep 24, 2015
Please fix Python style issue: |
There was a problem hiding this comment.
this should be aligned with tests,. you can run dev/lint-python to check style locally.
gliptak
commented
Sep 24, 2015
@mengxr Thanks for the local lint pointer |
SparkQA
commented
Sep 24, 2015
Test build #42980 has finished for PR 8323 at commit
|
mengxr
commented
Sep 24, 2015
@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 |
shaneknapp
commented
Sep 24, 2015
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 notifications@github.com
|
gliptak
commented
Sep 25, 2015
@mengxr Revised. |
SparkQA
commented
Sep 25, 2015
Test build #42996 has finished for PR 8323 at commit
|
mengxr
commented
Sep 25, 2015
@shaneknapp I created https://issues.apache.org/jira/browse/SPARK-10830 and assigned it to you. |
mengxr
commented
Sep 25, 2015
test this please |
SparkQA
commented
Sep 25, 2015
Test build #43015 has finished for PR 8323 at commit
|
mengxr
commented
Sep 28, 2015
test this please |
mengxr
commented
Sep 28, 2015
unittest-xml-reporting is installed on AMPLab Jenkins. So let's call Jenkins again. |
SparkQA
commented
Sep 29, 2015
Test build #1821 has finished for PR 8323 at commit
|
gliptak
commented
Sep 29, 2015
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 |
shaneknapp
commented
Sep 29, 2015
i'll take a look at the config tomorrow On Mon, Sep 28, 2015 at 6:02 PM, gliptak notifications@github.com wrote:
|
mengxr
commented
Sep 30, 2015
test this please |
SparkQA
commented
Sep 30, 2015
Test build #43109 has finished for PR 8323 at commit
|
mengxr
commented
Sep 30, 2015
test this please |
SparkQA
commented
Sep 30, 2015
Test build #43113 has finished for PR 8323 at commit
|
gliptak
commented
Sep 30, 2015
@mengxr Thank you for guiding this |
mengxr
commented
Oct 2, 2015
test this please |
mengxr
commented
Oct 2, 2015
it seems that this PR has a higher-than-normal failure rate .. I don't know why. +@davies |
SparkQA
commented
Oct 2, 2015
Test build #43176 has finished for PR 8323 at commit
|
mengxr
commented
Oct 5, 2015
test this please |
SparkQA
commented
Oct 5, 2015
Test build #43252 has finished for PR 8323 at commit
|
JoshRosen
commented
Oct 6, 2015
Huh, looks like the last two failures were for the same PySpark test: |
JoshRosen
commented
Oct 6, 2015
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? |
JoshRosen
commented
Oct 6, 2015
@gliptak, can you try to reproduce the failure locally? See |
gliptak
commented
Oct 7, 2015
@JoshRosen I do not have python2.6 installed (or available as a package) locally |
gliptak
commented
Oct 8, 2015
@JoshRosen How are the doctest-s triggered on the commandline and in Jenkins? |
gliptak
commented
Oct 14, 2015
What is the next step on this pull request? Thanks |
mengxr
commented
Oct 16, 2015
@gliptak I had an offline discussion with @davies . Let's do the following:
Then we can run Jenkins again and see whether it works. |
SparkQA
commented
Oct 16, 2015
Test build #43863 has finished for PR 8323 at commit
|
davies
commented
Oct 16, 2015
Right now, all the Python unit tests are in the package of |
gliptak
commented
Oct 16, 2015
@davies Not that I see. I opened xmlrunner/unittest-xml-reporting#95 to discuss. |
gliptak
commented
Oct 16, 2015
@JoshRosen I opened xmlrunner/unittest-xml-reporting#94 to discuss doctests processing. |
mengxr
commented
Oct 22, 2015
This looks good to me. I think we can address the test namespace issue in a later PR. @davies@JoshRosen ? |
davies
commented
Oct 22, 2015
LGTM, merging this into master, thanks! |
gliptak
commented
Oct 22, 2015
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/ |
gliptak
commented
Oct 24, 2015
Adding packages to XMLs at #9263 |
WIP