View Issue Details

IDProjectCategoryView StatusLast Update
0001557GNUnetcore servicepublic2010-07-03 20:55
Reportermrwiggles Assigned ToChristian Grothoff  
PriorityhighSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0001557: Send key fails in core
DescriptionThe testing testcases sometimes wait for a timeout or fail because of a failed set key operation (which then reschedules after a timeout).

The testing framework operates as follows:
1) Start peers, get hello from each.
2) When asked to connect two peers, give the hello of one peer to the other.
   2a) Wait for core to notify peers connected.

Somehow, when this process happens core tries to transmit a set key request (which fails for some reason). And then the timeout is hit. This causes testcases on fast machines to take approximately the initial set key timeout before completing. For some reason on slow machines (specifically the sparcbot) an initial set key failure causes the peers to never connect, even on retries. Whether this is a related problem or a HELLO timeout or something else is unclear.
  
TagsNo tags attached.

Activities

mrwiggles

2010-05-12 16:14

reporter   ~0004015

Reducing the initial timeout for set key operations seems to reduce test case failures, though it clearly doesn't solve the problem!

mrwiggles

2010-05-12 16:21

reporter   ~0004016

Can be reproduced (even on fast machine) by running src/testing/test_testing_topology_clique a number of times. A delay can be observed *sometimes*, which with core debugging enabled reveals what's happening.

Christian Grothoff

2010-05-25 18:50

manager   ~0004017

I fixed a few issues in this area (down to util's connection API and back). So I suspect this is gone, but would be good if you could check.

mrwiggles

2010-07-02 11:01

reporter   ~0004055

Seemingly fixed as of now. Set key failures are only happening when running thousands of nodes. So closing unless sparcbot or slower machines start failing testcases again.

Issue History

Date Modified Username Field Change
2010-05-12 16:04 mrwiggles New Issue
2010-05-12 16:14 mrwiggles Note Added: 0004015
2010-05-12 16:21 mrwiggles Note Added: 0004016
2010-05-25 18:50 Christian Grothoff Note Added: 0004017
2010-05-25 18:50 Christian Grothoff Status new => feedback
2010-07-02 11:01 mrwiggles Note Added: 0004055
2010-07-02 11:02 mrwiggles Assigned To => Christian Grothoff
2010-07-02 11:02 mrwiggles Status feedback => resolved
2010-07-02 11:02 mrwiggles Resolution open => fixed
2010-07-03 20:55 Christian Grothoff Status resolved => closed