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

test_resolve.cpp fails #52

Open
mfbalin opened this issue Sep 3, 2023 · 4 comments
Open

test_resolve.cpp fails #52

mfbalin opened this issue Sep 3, 2023 · 4 comments

Comments

@mfbalin
Copy link
Contributor

mfbalin commented Sep 3, 2023

I have compiled inside a docker container with G++11. After running the tests, all but a single fail is observed. The test output below:

root@a100cse:/localscratch/senders-io/build/tests# ./test_sio 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
test_sio is a Catch v2.13.6 host application.
Run with -? for options

-------------------------------------------------------------------------------
async::resolve - Resolve ipv4 localhost
-------------------------------------------------------------------------------
/localscratch/senders-io/tests/net/test_resolve.cpp:22
...............................................................................

/localscratch/senders-io/tests/net/test_resolve.cpp:22: FAILED:
due to unexpected exception with message:
  Servname not supported for ai_socktype

===============================================================================
test cases:  87 |  86 passed | 1 failed
assertions: 306 | 305 passed | 1 failed
@maikel
Copy link
Owner

maikel commented Sep 3, 2023

Interesting. I will look into that.

@maikel
Copy link
Owner

maikel commented Sep 3, 2023

It might be due to a minimal /etc/services file. Can you post its content here, please? It might be better to change the test from using service "http" to some numerical string such as "80" (or anything else). In fact it might show that an overload is needed without a specified service, since that is a optional for the underlying calls.

@mfbalin
Copy link
Contributor Author

mfbalin commented Sep 3, 2023

/etc/services was missing. apt install netbase fixed the issue. Thanks. I guess docker environments can be really different compared to bare metal Linux installations.

@maikel
Copy link
Owner

maikel commented Sep 3, 2023

The test just assumed /etc/services to exists which might be bad. I will fix that.

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

No branches or pull requests

2 participants