-
Notifications
You must be signed in to change notification settings - Fork 80
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(binding-coap): await
all calls of coapServer.stop()
#1094
Conversation
await´ all calls of
coapServer.stop()`await
all calls of coapServer.stop()
63f709e
to
e3c7fd0
Compare
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## master #1094 +/- ##
=======================================
Coverage 75.32% 75.32%
=======================================
Files 80 80
Lines 16057 16057
Branches 1503 1503
=======================================
Hits 12095 12095
Misses 3923 3923
Partials 39 39 ☔ View full report in Codecov by Sentry. |
As I remembered that using both |
Just saw this video yesterday 😄 |
:D I also had that one in mind ;) |
In the context of #1086 and #1077, I noticed that in the CoAP tests, not all invocations of
coapServer.stop()
are actually explicitly being awaited which might cause the CI to hang if there is an unexpected error.This PR makes a couple of minor adjustments to improve the cleanup of resources and fix this potential problem (although I am not sure to which extent it is actually a problem to begin).