-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add test for invalid listen scheme #139
Conversation
This PR also originally included ansible/receptor#93 (comment), but that test is currently failing, and it doesn't even assert correct behaviour, so it seems a bit odd to add right now. |
Quite a few tests are failing, and I can reproduce locally, even without this PR. Very annoying. |
Build succeeded.
|
Rebased and added a second commit which tests #138. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Rebased, and added tests for ansible/receptor#153 |
BTW the automated tests added by this PR currently pass very consistently against devel. I don't recall the last time I've seen any of them fail, if ever. |
This is useful in cases where the listen string lacks a port, like: receptor://127.0.0.1 This change will ensure that the `listen_port` method better adheres to its signature (by more consistently returning an int) and simplify certain tests, e.g. by dropping the `_wait_for_conns` method added in ansible/receptor#139
Dropped the |
If no port number is specified, then receptor should listen on port 8888. See: ansible/receptor#138
No description provided.