aboutsummaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2010-05-31 19:32:25 +0000
committerChristian Grothoff <christian@grothoff.org>2010-05-31 19:32:25 +0000
commitb80779dcac50d599d078b233ab323cbcc88e9218 (patch)
tree2c08326182652ab2536c52ff6fb28fdecb7e1115 /TODO
parent0979933d4ed20341233a939723f8d069a26a3dd9 (diff)
downloadgnunet-b80779dcac50d599d078b233ab323cbcc88e9218.tar.gz
gnunet-b80779dcac50d599d078b233ab323cbcc88e9218.zip
update
Diffstat (limited to 'TODO')
-rw-r--r--TODO3
1 files changed, 2 insertions, 1 deletions
diff --git a/TODO b/TODO
index da8e2d07b..d7d3e902f 100644
--- a/TODO
+++ b/TODO
@@ -1,9 +1,10 @@
10.9.0pre1: 10.9.0pre1:
2* FS: [CG] 2* FS: [CG]
3 - Migration test error scenarios: 3 - Migration test error scenarios:
4 1) peers fail to connect (very, very rare) 4 1) peers fail to connect (very, very rare) => maybe explained with bandwidth bug discovered with transport test
5 2) 1 out of 3 bits of content fails to migrate (destination peer never sees it); 5 2) 1 out of 3 bits of content fails to migrate (destination peer never sees it);
6 suspicion: core packs two migration messages into one, and someone throws away the 2nd half! 6 suspicion: core packs two migration messages into one, and someone throws away the 2nd half!
7 => likely reproduced with new core api reliability test (which still fails)
7 3) client fails to connect to FS service for download (requests never make it to FS) 8 3) client fails to connect to FS service for download (requests never make it to FS)
8 FS was running initially, but is shut down around the time the source peer (!) 9 FS was running initially, but is shut down around the time the source peer (!)
9 is supposed to die; the OTHER FS service (the one that was supposed to die) is still up! 10 is supposed to die; the OTHER FS service (the one that was supposed to die) is still up!