> > Getting these errors when tried to run locally
> > http://paste.ubuntu.com/24057813/
>
> Yes. It is because snapcraft helpers were updated to run the commands over
> ssh.
> I was able to run the tests by connecting by ssh to my localhost. However, I
> needed to add the environment variables each time I sens the command via
> ssh... But it will not be needed once we have the containers setup in place,
> because we configure the env variables as part of the setup process.
>
> If you still would like to tests it locally, add in
> ~/.config/ecosystem_tests.cfg:
> [user]
> user_email=^STORE_USER^
> user_password=^STORE_PASSWORD^
> hostname_remote=localhost
> username_remote=^LOCAL_USERNAME^
> port_remote=22
>
> And replace in snappy_ecosystem_tests/utils/ssh.py the function run_command
> by:
> http://paste.ubuntu.com/24058432/
>
> As I said it is just a workaround to be able to run the tests on the
> localhost, it will not be needed once we have the setup environment in place.
OK, then I think we should have the setup environment changes landed first with updated readme instructions.
> > Getting these errors when tried to run locally paste.ubuntu. com/24057813/ ecosystem_ tests.cfg: ^STORE_ USER^ ^STORE_ PASSWORD^ remote= localhost remote= ^LOCAL_ USERNAME^ ecosystem_ tests/utils/ ssh.py the function run_command paste.ubuntu. com/24058432/
> > http://
>
> Yes. It is because snapcraft helpers were updated to run the commands over
> ssh.
> I was able to run the tests by connecting by ssh to my localhost. However, I
> needed to add the environment variables each time I sens the command via
> ssh... But it will not be needed once we have the containers setup in place,
> because we configure the env variables as part of the setup process.
>
> If you still would like to tests it locally, add in
> ~/.config/
> [user]
> user_email=
> user_password=
> hostname_
> username_
> port_remote=22
>
> And replace in snappy_
> by:
> http://
>
> As I said it is just a workaround to be able to run the tests on the
> localhost, it will not be needed once we have the setup environment in place.
OK, then I think we should have the setup environment changes landed first with updated readme instructions.