Closed
Conversation
The test had `Closing connection 0` in its expectations, but a stripfile expression that removes such lines. No recent changes, but started failing this morning. Too little coffee for me? Or what triggered this?
Fix all lookups of the port a server is using by - unlinking the portfile before the start - waiting `timeout` seconds for the port file to exist and contain a positive number - check results and fail server start when port could not be determined builds on top of curl#17515
bagder
approved these changes
Jun 2, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fix all lookups of the port a server is using by
timeoutseconds for the port file to exist and contain a positive numberbuilds on top of #17515