[GNUnet-SVN] r21968 - in gnunet-java: . src/org/gnunet/testing

[gnunet]

Author: dold
Date: 2012-06-13 16:17:46 +0200 (Wed, 13 Jun 2012)
New Revision: 21968

Modified:
   gnunet-java/ISSUES
   gnunet-java/src/org/gnunet/testing/TestingSubsystem.java
Log:
issues, text

Modified: gnunet-java/ISSUES
===================================================================
--- gnunet-java/ISSUES  2012-06-13 14:06:49 UTC (rev 21967)
+++ gnunet-java/ISSUES  2012-06-13 14:17:46 UTC (rev 21968)
@@ -16,10 +16,8 @@
  * for private/anonymous inner classes: 10-20% overhead, measured over 100M 
calls
  * only issue left: visit methods have to be public, but this is a non issue.
 
-
 * review the RequestQueue mechanism
 
-
 * Statistics:
  * currently watches can't be canceled on the service level, only on the api 
level, is this intentional?
 => fine for now
@@ -137,14 +135,27 @@
 
 ============================================================
 
-* test now run on the cobertura account :)
+* tests now run on the cobertura account :)
  * see https://gnunet.org/cobertura/
+ * gnunet needs to compiled with --disable-nls to work on the server
+ * cronjob added
+ * could/should we report the success of JUnit tests?
+  * (as somehow my bugs only seem to show when running on another system ;)
 
-* needed for testing the server: getting an unused port with java
+* gnunet-java now can now start/restart services for testing with the testing 
wrapper executable
+ * i duplicated the code for GNUNET_TESTING_service_run_restartable
+  * now passes the Peer to main, which can start/stop it
+  * probably also should pass the config file name (not only the handle)
+   * how about a GNUNET_TESTING_peer_get_config_path?
+ * what about windows?
 
-gnunet needs to compiled with --disable-nls to work on the cobertura accout
+* server/service:
+ * needed for testing the server: getting an unused port with java
+ * how do we test the signal pipeline?
+  * probably with runin arm in a testing peer, but then we would also have to 
talk to arm
 
 
+the following notes are old:
 * we are still not able to test "temporary destruction"
  * because every time a new port may be generated
  * we need a way to kill a service and run it with the same config
@@ -164,13 +175,14 @@
  * currently we check availability of data on stderr.
 
 
-
 PEERINFO_GET vs PEERINFO_GET_ALL
  * if we have PEERINFO_GET_ALL, why is the peer-field in ListPeerMessage(with 
type=PEERINFO_GET) empty?
 
 
 * are peerinfo requests queued?
  * i remember discussing peerinfo as a compilicated example for a general 
message queueing implementation. why?
+ * if we have to queue: how about a "choke/release" for the outgoing message 
queue?
+  * otherwise we don't know which requests belongs to which response
 * can peerinfo return more than one record per peer?
 
 

Modified: gnunet-java/src/org/gnunet/testing/TestingSubsystem.java
===================================================================
--- gnunet-java/src/org/gnunet/testing/TestingSubsystem.java    2012-06-13 
14:06:49 UTC (rev 21967)
+++ gnunet-java/src/org/gnunet/testing/TestingSubsystem.java    2012-06-13 
14:17:46 UTC (rev 21968)
@@ -39,7 +39,6 @@
 
     private Process p;
     private BufferedReader reader;
-    private BufferedReader errReader;
     private OutputStreamWriter writer;
     private Configuration cfg;
 
@@ -121,7 +120,7 @@
         } catch (IOException e) {
             throw new TestingSetup.SetupException(e);
         }
-        String response = null;
+        String response;
         logger.debug("waiting for gnunet-testing-run-service to respond to 
restart");
         try {
             response = reader.readLine();