Use default loop in testsuite and close server and connection leftovers#283
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
clue approved these changes Jan 13, 2022
Member
clue left a comment
clue left a comment There was a problem hiding this comment.
@SimonFrings Thanks for looking into this, changes LGTM! 
WyriHaximus approved these changes Jan 13, 2022
This was referenced Aug 3, 2022
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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.
I noticed that this testsuite still uses the old eventloop implementation. After I changed everything to the new default loop some tests got stuck in execution, because other tests didn't close their servers/connections.
Builds on top of #260 and clue/reactphp-block#60.