[
https://issues.apache.org/jira/browse/SLIDER-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191846#comment-14191846
]
ASF subversion and git services commented on SLIDER-570:
--------------------------------------------------------
Commit 1f98074f16e7840d11727d9bcf1efb5a7858595e in incubator-slider's branch
refs/heads/develop from [~ste...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=1f98074 ]
SLIDER-570: AgentClusterLifecycleIT -> lookup/appId driven on thaw operations
> funtests to grab last (failing) app report on a launch failuret
> ---------------------------------------------------------------
>
> Key: SLIDER-570
> URL: https://issues.apache.org/jira/browse/SLIDER-570
> Project: Slider
> Issue Type: Sub-task
> Components: test
> Affects Versions: Slider 0.60
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: Slider 0.60
>
>
> when an AM doesn't start in a functional test the log message is simply that
> the app didn't come up in the time limit.
> We can do better: on a launch failure
> # enum the app records for that app instance name
> # grab the latest one
> # print it to the junit log
> # include it in the failure exception thrown
> This will make launch failure causes more obvious, and enable more meaningful
> bug reports to be filed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
