Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Calling via Cucumber (Aruba) steps fails #31

Closed
hedgehog opened this Issue · 2 comments

3 participants

@hedgehog

As far as I can tell Aruba passes the correct command around and runs it.
So I suspect this might not be trivial to track down the cause of:

Using Aruba's step definition (with 'lucid64-base' or lucid64-base):

    Given I successfully run `vagrant basebox export 'lucid64-base' 2>&1 |tee lucid64-base-export.log`

I get:

RuntimeError: Exit status was 1. Output:
"export" was called incorrectly. Call as "vagrant basebox export [NAME]".
@jedi4ever
Owner

I suspect that the way aruba passes args to the command causes this.
I would test print with ARGV in the vagrant binary to see if these get passed as different args, or end up all in ARGV[1]

@miketheman
Collaborator

Closing this due to age, no response, and not being part of the core veewee feature set.

@miketheman miketheman closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.