[
https://issues.apache.org/jira/browse/SPARK-25924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shane knapp reopened SPARK-25924:
---------------------------------
this is actually causing builds that don't test k8s to fail:
https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/4728/console
{noformat}
Archiving artifacts
ERROR: No artifacts found that match the file pattern
"**/core/target/unit-tests.log
**/resource-managers/kubernetes/integration-tests/target/surefire-reports/*.xml
**/resource-managers/kubernetes/integration-tests/target/integration-tests.log".
Configuration error?
ERROR: java.lang.InterruptedException: no matches found within 10000
Build step 'Archive the artifacts' changed build result to FAILURE{noformat}
> 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
> Assignee: shane knapp
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
