[ https://issues.apache.org/jira/browse/SPARK-25924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685670#comment-16685670 ]
shane knapp commented on SPARK-25924: ------------------------------------- ok, so that's weird... i was watching the filesystem on the worker that this build ran on: [https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/5000/] ...and there were logs showing up: ``` jenkins@research-jenkins-worker-07:~/workspace/testing-k8s-prb-make-spark-distribution-unified$ find . | grep "tests.log" ./resource-managers/kubernetes/integration-tests/target/integration-tests.log ./core/target/unit-tests.log ``` however, when the build finished it couldn't find the logs... sadly, as soon as this build finished, a NEW build immediately launched on the same worker and wiped the workspace clean before i could archive it and look deeper. triggered another build to try and see what's going on. :\ > 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