[jira] [Resolved] (SPARK-3193) output errer info when Process exitcode not zero

["Prashant Sharma (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prashant Sharma resolved SPARK-3193.
------------------------------------

    Resolution: Invalid

[Verbatim from my comment on PR  ]

Hey !, Thanks for raising this concern.

The convention in spark is that we look in the [sub-project]/target/unit-tests.log. And this is applicable to all test suits. So when you saw a particular test fail on the Jenkins, you can rerun that test locally and then check that unit-tests.log file for that sub-project.

I hope this helps. You can close this PR if you are convinced.

P.S: May be we can expand our wiki page with this information.


> output errer info when Process exitcode not zero
> ------------------------------------------------
>
>                 Key: SPARK-3193
>                 URL: https://issues.apache.org/jira/browse/SPARK-3193
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 1.0.2
>            Reporter: wangfei
>
> I noticed that sometimes pr tests failed due to the Process exitcode != 0:
> DriverSuite: 
> Spark assembly has been built with Hive, including Datanucleus jars on classpath 
> - driver should exit after finishing *** FAILED *** 
>    SparkException was thrown during property evaluation. (DriverSuite.scala:40) 
>      Message: Process List(./bin/spark-class, org.apache.spark.DriverWithoutCleanup, local) exited with code 1 
>      Occurred at table row 0 (zero based, not counting headings), which had values ( 
>        master = local 
>      ) 
>  
> [info] SparkSubmitSuite:
> [info] - prints usage on empty input
> [info] - prints usage with only --help
> [info] - prints error with unrecognized options
> [info] - handle binary specified but not class
> [info] - handles arguments with --key=val
> [info] - handles arguments to user program
> [info] - handles arguments to user program with name collision
> [info] - handles YARN cluster mode
> [info] - handles YARN client mode
> [info] - handles standalone cluster mode
> [info] - handles standalone client mode
> [info] - handles mesos client mode
> [info] - handles confs with flag equivalents
> [info] - launch simple application with spark-submit *** FAILED ***
> [info]   org.apache.spark.SparkException: Process List(./bin/spark-submit, --class, org.apache.spark.deploy.SimpleApplicationTest, --name, testApp, --master, local, file:/tmp/1408854098404-0/testJar-1408854098404.jar) exited with code 1
> [info]   at org.apache.spark.util.Utils$.executeAndGetOutput(Utils.scala:872)
> [info]   at org.apache.spark.deploy.SparkSubmitSuite.runSparkSubmit(SparkSubmitSuite.scala:311)
> [info]   at org.apache.spark.deploy.SparkSubmitSuite$$anonfun$14.apply$mcV$sp(SparkSubmitSuite.scala:291)
> [info]   at org.apache.spark.deploy.SparkSubmitSuite$$anonfun$14.apply(SparkSubmitSuite.scala:284)
> [info]   at org.apacSpark assembly has been built with Hive, including Datanucleus jars on classpath
> refer to 
> https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18688/consoleFull
> https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19118/consoleFull
> we should output the process error info when failed, this can be helpful for diagnosis.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org