[
https://issues.apache.org/jira/browse/SPARK-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312331#comment-16312331
]
Hyukjin Kwon commented on SPARK-7721:
-------------------------------------
I (and possibly few committers given [the comment
above|https://issues.apache.org/jira/browse/SPARK-7721?focusedCommentId=14551198&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14551198])
would run this though .. but yes, sure, it should become actually powerful
when we can run it automatically.
If we are all fine to have a single up-to-date coverage site ("Simplest one")
for now, it's pretty easy and possible. It's just what I have done so far here
- https://spark-test.github.io/pyspark-coverage-site and the only thing I
should do is to make this automatic, clone the latest commit bit and push it.
I know it's better to keep the history of coverages and leave the link in each
PR ("Another one") and in this case we should consider how to keep the history
of the coverages, etc. This is where I should investigate more and verify the
idea.
Will anyway test and investigate the integration more and try the "Another one"
way too. If I fail, I think we can fall back to "Simplest one" for now. Does
this sounds good to you? In this way, I think I can make sure we can run this
automatically eventually.
BTW, can you take a look for https://github.com/apache/spark/pull/20151 too?
This way we can make the changes separate for Coverage only and I am trying to
isolate such logics as much as we can in case we can bring better idea in the
future.
> Generate test coverage report from Python
> -----------------------------------------
>
> Key: SPARK-7721
> URL: https://issues.apache.org/jira/browse/SPARK-7721
> Project: Spark
> Issue Type: Test
> Components: PySpark, Tests
> Reporter: Reynold Xin
>
> Would be great to have test coverage report for Python. Compared with Scala,
> it is tricker to understand the coverage without coverage reports in Python
> because we employ both docstring tests and unit tests in test files.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
