You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2018/11/02 17:10:00 UTC

[jira] [Commented] (SPARK-25924) k8s integration tests on jenkins do not save log output

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

Marcelo Vanzin commented on SPARK-25924:
----------------------------------------

[~shaneknapp], it seems that the ITs do generate a {{unit-tests.log}} file like other tests (at least when I run them through sbt with my patch that's under review).

Could you double check that it's also the case with maven on jenkins, and then publish those logs as an artifact for the IT runs? Thx

> k8s integration tests on jenkins do not save log output
> -------------------------------------------------------
>
>                 Key: SPARK-25924
>                 URL: https://issues.apache.org/jira/browse/SPARK-25924
>             Project: Spark
>          Issue Type: Improvement
>          Components: Kubernetes
>    Affects Versions: 3.0.0
>            Reporter: Marcelo Vanzin
>            Priority: Major
>
> The k8s integration test on jenkins does not seem to save any log files. So when the tests fail, you have extremely little information about what happened.
> Especially with recent changes to the code, where even child process output is only logged and not printed as part of assertions anymore.
> The normal PR builder saves a bunch of log files that are useful for debugging when things go wrong; these jobs should do the same.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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