gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnurl] 63/264: TODO: Use "random" ports for the test servers


From: gnunet
Subject: [gnurl] 63/264: TODO: Use "random" ports for the test servers
Date: Thu, 30 Apr 2020 16:06:06 +0200

This is an automated email from the git hooks/post-receive script.

nikita pushed a commit to branch master
in repository gnurl.

commit 4b355dd13b29eb8ef93d20c60b418004d8b8d6b1
Author: Daniel Stenberg <address@hidden>
AuthorDate: Sun Mar 22 23:30:09 2020 +0100

    TODO: Use "random" ports for the test servers
---
 docs/TODO | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/TODO b/docs/TODO
index fbf2d2520..ddf3652b8 100644
--- a/docs/TODO
+++ b/docs/TODO
@@ -163,6 +163,7 @@
  20.6 Use the RFC6265 test suite
  20.7 Support LD_PRELOAD on macOS
  20.8 Run web-platform-tests url tests
+ 20.9 Use "random" ports for the test servers
 
  21. Next SONAME bump
  21.1 http-style HEAD output for FTP
@@ -1096,6 +1097,17 @@ that doesn't exist on the server, just like 
--ftp-create-dirs.
 
  See https://github.com/curl/curl/issues/4477
 
+20.9 Use "random" ports for the test servers
+
+ Instead of insisting and using fixed port numbers for the tests (even though
+ they can be changed with a switch), consider letting each server pick a
+ random available one at start-up, store that info in a file and let the test
+ suite use that.
+
+ We could then remove the "check that it is our server that's running"-check
+ and we would immediately detect when we write tests wrongly to use hard-coded
+ port numbers.
+
 21. Next SONAME bump
 
 21.1 http-style HEAD output for FTP

-- 
To stop receiving notification emails like this one, please contact
address@hidden.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]