View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005091 | GNUnet | cadet service | public | 2017-06-22 22:22 | 2018-06-07 00:24 |
| Reporter | xrs | Assigned To | lurchi | ||
| Priority | normal | Severity | minor | Reproducibility | random |
| Status | closed | Resolution | open | ||
| Platform | x86_64 | OS | archlinux | OS Version | head |
| Product Version | Git master | ||||
| Target Version | 0.11.0pre66 | Fixed in Version | 0.11.0pre66 | ||
| Summary | 0005091: Multicast services uses cadet to make connection, but sometimes no transmission happens | ||||
| Description | The test does the following: 1. Create two peers, origin and member. 2. Peer Origin creates a multicast group and joins it. 3. Peer Member tryies to join the multicast group by sending a join request. 4. Peer Origin receives it and decides to accept peer member. 5. Peer member receives the positive decision. 6. Peer member sends a ping as message. 7. Peer origin receives the ping message and sends a pong message to the multicast group. 8. Peer member receives the pong messages and the test stops successfully. This process is executed when "make check" is called. The two peers start, but as they use no standard ports they need a hostlist server to find each other. Thus I have a hostlist server running. All peers run in an isolated environment (private network). I use a script to watch them connect to each other by asking every second "gnunet-peerinfo -c <peer-config>" for both peers. I see the two peers connect to the hostlist server and after a few seconds connect to each other. After that I expect to see the process being carried out. If executed repeatedly the test randomly succeeds after 15 seconds of fails with a timeout. It's more or less a 50/50 chance. See for comparison: * test_multicast_multipeer.sane.log * test_multicast_multipeer.bad.log I'm not sure if the problem is with cadet, multicast or something else. I added two more (positive/negativ) tests with cadet debug logs hoping that somebody can interprete them better than I. See for comparison: * test_multicast_multipeer-with_cadet_logs.sane.log * test_multicast_multipeer-with_cadet_logs.bad.log | ||||
| Steps To Reproduce | cd src/multicast/ GNUNET_FORCE_LOG="test-multicast-multipeer;;;;DEBUG/multicast;;;;DEBUG/cadet;;;;DEBUG" make check; | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-06-22 22:22 | xrs | New Issue | |
| 2017-06-22 22:22 | xrs | Status | new => assigned |
| 2017-06-22 22:22 | xrs | Assigned To | => Bart Polot |
| 2017-06-22 22:22 | xrs | File Added: test_multicast_multipeer.tar.gz | |
| 2017-07-14 13:25 | xrs | Note Added: 0012334 | |
| 2017-07-24 18:58 | Christian Grothoff | Assigned To | Bart Polot => lurchi |
| 2017-07-24 18:58 | Christian Grothoff | Status | assigned => resolved |
| 2017-07-24 18:58 | Christian Grothoff | Fixed in Version | => 0.11.0pre66 |
| 2017-07-24 18:58 | Christian Grothoff | Target Version | => 0.11.0pre66 |
| 2018-06-07 00:24 | Christian Grothoff | Status | resolved => closed |