[
https://issues.apache.org/jira/browse/SLIDER-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152584#comment-14152584
]
Gour Saha commented on SLIDER-448:
----------------------------------
Introduced property {{slider.test.agent.am.failures.enabled}} set to {{false}}
by default, so it will not run the AM failure tests. Once we get a generic
(non-vagrant specific) way to kill AM working, we will incorporate smarter
patches like the one [~billie.rinaldi] provided.
Until then AM failure IT tests can be run in a vagrant VM only and requires
{{slider.test.agent.am.failures.enabled}} to be set to true in
slider-client.xml and {{vagrant.current.working.dir}} to be set to the
directory which contains the Vagrantfile.
> 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)
