-
Notifications
You must be signed in to change notification settings - Fork 3k
IPCore unittests improvements #11612
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
IPCore unittests improvements #11612
Conversation
e061894
to
1544b17
Compare
@michalpasztamobica, thank you for your changes. |
@ARMmbed/mbed-os-maintainers Please proceed with this |
CI started |
Test run: FAILEDSummary: 1 of 1 test jobs failed Failed test jobs:
|
I must admit I couldn't find the exact error message, I just see:
And then in the faulty job I don't see any failing test... I believe the failure is relevant, but I fail to see the rootcause... |
@michalpasztamobica I checked the build logs and it seems Valgrind reports a memory leak for netsocket/NetworkInterface test (TestNetworkInterface_correct_event_listener_per_interface_Test) |
Thanks, @AnttiKauppila ! |
For the following classes: * DTLSSocket * NetworkInterface * TLSSocketWrapper
Close should not take place in case there is someone reading or writing to the socket.
316c52d
to
66c4b13
Compare
We will, we are finilizing 5.14.1 jobs at the moment, will trigger asap |
CI started |
Test run: SUCCESSSummary: 1 of 1 test jobs passed |
Description
A result of a short revisit to the unittests of socket classes:
InternetSocket::close()
tests which asynchronously block the closing when there is an active reader or writer (using C++11's async and chrono, which were enabled recently)get_interface_name()
etc.)Pull request type
Reviewers
@AnttiKauppila
@SeppoTakalo
@VeijoPesonen
Release Notes