Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

integration tests broken because of Weave Net 2.0 changes #2640

Closed
rade opened this issue Jun 24, 2017 · 1 comment
Closed

integration tests broken because of Weave Net 2.0 changes #2640

rade opened this issue Jun 24, 2017 · 1 comment
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it

Comments

@rade
Copy link
Member

rade commented Jun 24, 2017

The latest release of Weave Net (2.0) removes the weave run command. Unfortunately we use that in several of our integration tests, which therefore fail.

@rade rade added the bug Broken end user or developer functionality; not working as the developers intended it label Jun 24, 2017
@rade rade changed the title integration tests brokenbecause the call weave run integration tests broken because they call weave run Jun 25, 2017
@rade rade self-assigned this Jun 25, 2017
@rade rade changed the title integration tests broken because they call weave run integration tests broken because of Weave Net 2.0 changes Jun 25, 2017
@rade
Copy link
Member Author

rade commented Jun 25, 2017

Some tests also look for a weaveproxy container, which no longer exists in Weave Net 2.0.

rade added a commit that referenced this issue Jun 25, 2017
make integration tests pass with latest Weave Net release (2.0)

Fixes #2640.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

1 participant