[
https://issues.apache.org/jira/browse/SPARK-26944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775117#comment-16775117
]
Alessandro Bellina edited comment on SPARK-26944 at 2/22/19 1:07 PM:
---------------------------------------------------------------------
Hmm, I have a subsequent build from the same PR, and I don't see a link to the
python tests either. Maybe I am looking in the wrong place?
[https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/102590/artifact/]
was (Author: abellina):
Hmm, I have a subsequent build from the same PR, and I don't see a link to the
python tests either. Maybe I am looking in the wrong place?
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/102590/artifact/
> Python unit-tests.log not available in artifacts for a build in Jenkins
> -----------------------------------------------------------------------
>
> Key: SPARK-26944
> URL: https://issues.apache.org/jira/browse/SPARK-26944
> Project: Spark
> Issue Type: Improvement
> Components: Build
> Affects Versions: 2.4.0
> Reporter: Alessandro Bellina
> Priority: Minor
>
> I had a pr where the python unit tests failed. The tests point at the
> `/home/jenkins/workspace/SparkPullRequestBuilder/python/unit-tests.log` file,
> but I can't get to that from jenkins UI it seems (are all prs writing to the
> same file?).
> {code:java}
> ========================================================================
> Running PySpark tests
> ========================================================================
> Running PySpark tests. Output is in
> /home/jenkins/workspace/SparkPullRequestBuilder/python/unit-tests.log{code}
> For reference, please see this build:
> https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/102518/console
> This Jira is to make it available under the artifacts for each build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
