[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=16685748#comment-16685748 ] shane knapp commented on SPARK-25924: - !Screen Shot 2018-11-13 at 1.17.50 PM.png! > 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 > Attachments: Screen Shot 2018-11-13 at 1.17.50 PM.png > > > 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
[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=16685713#comment-16685713 ] shane knapp commented on SPARK-25924: - think i got it! i had the format wrong for the 'archive artifacts' fileglobs in the build config, and jenkins didn't warn me that i needed commas vs whitespace between each pattern for it work work as expected. launching another build and will confirm afterwards if the archive step worked. > 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
[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=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
[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=16685636#comment-16685636 ] shane knapp commented on SPARK-25924: - weird. i'll launch a build and see what's going on... none of the recent builds have logs on the physical workers. On Tue, Nov 13, 2018 at 10:10 AM Marcelo Vanzin (JIRA) -- Shane Knapp UC Berkeley EECS Research / RISELab Staff Technical Lead https://rise.cs.berkeley.edu > 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
[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=16685562#comment-16685562 ] Marcelo Vanzin commented on SPARK-25924: Hey [~shaneknapp], you maked this as fixed but I still don't see the logs on the jenkins build page? e.g. https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/4958/ > 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
[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=16673711#comment-16673711 ] shane knapp commented on SPARK-25924: - ok done for real! > 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
[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=16673674#comment-16673674 ] shane knapp commented on SPARK-25924: - alright, waiting for the next test to run before closing this. > 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
[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=16673655#comment-16673655 ] shane knapp commented on SPARK-25924: - ah, found the right log! :) ./resource-managers/kubernetes/integration-tests/target/integration-tests.log adding that now to the build config. > 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
[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=16673624#comment-16673624 ] shane knapp commented on SPARK-25924: - done. i'll close this after we have a failing k8s test build to confirm that this works. :) > 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
[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=16673623#comment-16673623 ] shane knapp commented on SPARK-25924: - i will copy the setup from the regular pull request builder to the k8s test... that should catch any/everything. > 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
[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=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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
