[
https://issues.apache.org/jira/browse/SPARK-24908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554597#comment-16554597
]
shane knapp commented on SPARK-24908:
-------------------------------------
i noticed lintr complaining in my PRB build
([https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/93509/console)]
:(
`Error: StartTag: invalid element name [68] Execution halted lintr checks
passed.`
so i checked other R-based PRB builds and saw the same thing:
pull request: https://github.com/apache/spark/pull/21835
associated build:
[https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/93402/consoleFull]
i'm guessing that this is a red herring.
> [R] remove spaces to make lintr happy
> -------------------------------------
>
> Key: SPARK-24908
> URL: https://issues.apache.org/jira/browse/SPARK-24908
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.3.1
> Reporter: shane knapp
> Assignee: shane knapp
> Priority: Critical
>
> during my travails in porting spark builds to run on our centos worker, i
> managed to recreate (as best i could) the centos environment on our new
> ubuntu-testing machine.
> while running my initial builds, lintr was crashing on some extraneous spaces
> in test_basic.R (see:
> [https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-sbt-hadoop-2.6-ubuntu-test/862/console)]
> after removing those spaces, the ubuntu build happily passed the lintr tests.
> i then tested this against a modified spark-master-test-sbt-hadoop-2.6 build
> (see
> [https://amplab.cs.berkeley.edu/jenkins/view/RISELab%20Infra/job/testing-spark-master-test-with-updated-R-crap/4/),]
> which scp'ed a copy of test_basic.R in to the repo after the git clone.
> everything seems to be working happily.
> i will be creating a pull request for this now.
>
> attn: [~felixcheung] [~shivaram] [~ifilonenko]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
