spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-1336) Reduce Verbosity of QA Scripts
Date Sun, 30 Mar 2014 06:40:14 GMT

    [ https://issues.apache.org/jira/browse/SPARK-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954597#comment-13954597
] 

ASF GitHub Bot commented on SPARK-1336:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/spark/pull/262


> Reduce Verbosity of QA Scripts
> ------------------------------
>
>                 Key: SPARK-1336
>                 URL: https://issues.apache.org/jira/browse/SPARK-1336
>             Project: Apache Spark
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Patrick Wendell
>            Assignee: Patrick Wendell
>
> Looking at the log output on jenkins is becoming a big data problem. In some cases, the
reason for failures is also confusing. There are a few ways we can make this more sane.
> - When running style checks, we should pipe the output to a file. The, if the tests fail
we should grep the file for "error" and print out a message saying that the style checks failed
and printing all the lines with failures. Probably this means writing a different script for
the style checks similar to what we have for the rat checks.
> - When running tests and running MIMA, we should try to silence all of the Resolving
messages. Something like this might work:
> sbt/sbt test |  grep -v "info.*Resolving"
> Ideally we want to do it in a way where we minimize the possibility of hiding legitimate
output. 
> - 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message