Ignore errors for EV_DELETE
in EventListener
#36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During tests execution, we've experienced the following error multiple times:
Environment:
After debugging, we noticed this is eventually received upon
server.stop()
invocation. The server was being started without any specific port, soPeasy
looked for an available one. ThefatalError
invocation causes the test execution to fail even when tests pass.In my opinion, this can be ignored for
EV_DELETE
.server.stop()
is usually invoked withintearDown()
so whatever happens toserver
while stopping is irrelevant for test execution results.