-
Notifications
You must be signed in to change notification settings - Fork 394
Behat Tests Fail #1681
Comments
@geerlingguy FYI this seems to be an issue with an interaction between BLT and Vagrant... what @grasmash and I are seeing is that the tests work fine "inside" the VM but when attempting to run outside for some reason things are looking in /vagrant (and when I do a vagrant exec pwd it also points at /vagrant instead of my repo root inside the vm). I just re-provisioned with a ssh_home variable in box/config.yml... any thoughts on what else might be going on here? |
The documentation here: http://docs.drupalvm.com/en/latest/extras/drupal-console/#remote-command-execution-using-vagrant-exec works when I manually create a Vagrantfile.local. With this in mind, should BLT create a Vagrantfile.local with this config during one of the settings phases? |
@geerlingguy Would you consider adding such setting to Drupal VM? |
I would rather go the route @typhonius recommends — see my notes in upstream PR geerlingguy/drupal-vm#1435 |
Wouldn't it just be a matter of using the path Also, you may be able to set the values in the already-existing https://github.com/acquia/blt/blob/8.x/scripts/drupal-vm/Vagrantfile (instead of having to also write a Vagrantfile.local). |
See PR #1688 — needs work, and I didn't test it, but I think that should be how it's set up in BLT. |
My system information:
When I run this command:
I get the following output:
And I expected this to happen:
The text was updated successfully, but these errors were encountered: