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

new version 0.14.2 #37

Merged
merged 4 commits into from
May 4, 2024
Merged

new version 0.14.2 #37

merged 4 commits into from
May 4, 2024

Conversation

choppsv1
Copy link
Collaborator

@choppsv1 choppsv1 commented May 4, 2024

  • new version 0.14.2
  • always fail mutest tests on bad json inputs
  • improve ssh-remote for common use-case of connecting to host connected devices
  • fix ready-cmd for python v3.11+

Previously only supported reaching nodes within the topology which
was actually a very uncommon use case (but the one that we can easily
test in CI).

Now we support reaching the server using the host network namespace.
It is far more likely that a router or server will be reachable over
a mgmt network connected to the host than within the munet network
namespace.
python3.11 and up forbid passing coroutines to asyncio.wait() now,
so create a list of tasks to pass instead.
Even if the user expects failure, bad json input will fail the test.

This was requested from users as the more useful functionality. Really,
the only useful reason to support expect_fail on bad json is for testing
the framework. Most users with expect_fail=True are looking at comparing
some valid json and having the comparison fail, and they want bad input
to still be flagged as a failure. If they want to test for bad json
they can use a normal `match_step()` test variant and match against the
expected "bad" json output.
@choppsv1 choppsv1 merged commit e1be538 into main May 4, 2024
6 checks passed
@choppsv1 choppsv1 deleted the chopps/test-0.14.2 branch May 4, 2024 04:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant