[
https://issues.apache.org/jira/browse/SLIDER-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149587#comment-14149587
]
Gour Saha commented on SLIDER-448:
----------------------------------
[~billie.rinaldi] I saw the same behavior too that when I was calling am
suicide from the groovy code it was not able to kill the AM. However when I ran
am-suicide from the command line it worked.
> AMFailuresIT needs vagrant
> --------------------------
>
> Key: SLIDER-448
> URL: https://issues.apache.org/jira/browse/SLIDER-448
> Project: Slider
> Issue Type: Bug
> Components: test
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Fix For: Slider 0.60
>
> Attachments: SLIDER-448-1.patch
>
>
> I'm getting a failure:
> AMFailuresIT.testAMKilledWithStateAMStartedAgentsStarted:87->killAMUsingVagrantShell:152
> Please set vagrant.current.working.dir to the directory which contains the
> Vagrantfile. Expression: dirCheck.exists()
> Maybe we should make the check for the vagrant.current.working.dir an
> "assume" rather than an "assert" so that it just skips that test if you don't
> have vagrant set up. The tests will not always be run on a vagrant cluster.
> Then we have the question of how to discover that you could be setting that
> property to enable an additional test ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
