gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] r9404 - gnunet/src/transport


From: gnunet
Subject: [GNUnet-SVN] r9404 - gnunet/src/transport
Date: Thu, 5 Nov 2009 01:29:25 -0700

Author: grothoff
Date: 2009-11-05 01:29:25 -0700 (Thu, 05 Nov 2009)
New Revision: 9404

Modified:
   gnunet/src/transport/test_plugin_transport.c
Log:
removing old comments

Modified: gnunet/src/transport/test_plugin_transport.c
===================================================================
--- gnunet/src/transport/test_plugin_transport.c        2009-11-05 08:26:42 UTC 
(rev 9403)
+++ gnunet/src/transport/test_plugin_transport.c        2009-11-05 08:29:25 UTC 
(rev 9404)
@@ -164,9 +164,6 @@
                         uint32_t challenge,
                         const char *sender_addr)
 {
-  /* Sailor: 'test_validation' should get here
-     if the validation worked; so we cancel the
-     "delayed" task that will cause failure */
   if (validation_timeout_task != GNUNET_SCHEDULER_NO_TASK)
     {
       GNUNET_SCHEDULER_cancel (sched, validation_timeout_task);
@@ -175,8 +172,6 @@
 
   GNUNET_assert (challenge == 42);
   
-  /* Sailor: if this is the last test, calling this function
-     here will end the process. */
   ok = 0; /* if the last test succeeded, report success */
   GNUNET_SCHEDULER_add_continuation (sched,
                                     &unload_task,
@@ -222,11 +217,6 @@
   soaddr.sin_len = sizeof (soaddr);
 #endif
   soaddr.sin_family = AF_INET;
-  /* Sailor: set this port to 2367 to see the
-     testcase fail after 30s (because validation
-     fails); obviously the test should be
-     modified to test both successful and
-     unsuccessful validation in the end... */
   soaddr.sin_port = htons(2368 /* FIXME: get from config! */);
   soaddr.sin_addr.s_addr = htonl (INADDR_LOOPBACK);
   api->validate (api->cls,
@@ -329,18 +319,7 @@
       /* FIXME: set some error code for main */
       return;
     } 
-  /* Sailor: if we had no real tests, we
-     could call this function
-     here to end the process; instead, I'll
-     show how one could run a single test below. 
-     Note that the test is not particularly well-written,
-     it just serves to illustrate (also,
-     the "validation_notification" function above is
-     part of the test.*/
-  if (0)
-    unload_plugins (NULL, cfg);
-  else
-    test_validation ();
+  test_validation ();
 }
 
 





reply via email to

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