[ https://issues.apache.org/jira/browse/SPARK-26944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835031#comment-16835031 ]
shane knapp commented on SPARK-26944: ------------------------------------- going through my queue, i found this and realized i hadn't verified that it worked. and it doesn't. because there's a bug in python/run-tests.py that overrides the output to a different location *after* it prints out where it plans on writing the log file to. PR incoming. this will need to be backported to 2.3 and 2.4. > 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 > Assignee: shane knapp > Priority: Minor > Attachments: Screen Shot 2019-03-05 at 12.08.43 PM.png > > > 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: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org