View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008689 | GNUnet | core service | public | 2024-03-31 17:37 | 2024-04-04 19:15 |
| Reporter | apteryx | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Product Version | 0.21.0 | ||||
| Summary | 0008689: test_communicator_bidirect-tcp fails (due to no DNS resolution?) | ||||
| Description | Hi, Testing the build of gnunet 0.21.0 from GNU Guix, I encountered this error: FAIL: test_communicator_bidirect-tcp ==================================== 2024-03-31T15:06:23.511052+0000 test_transport_communicator-17123 INFO Identity of peer 0 is P2TF2DYZ35GTBPGSYGQJSG0H5594QS2JW6TNWFPYMYYD9B8CTJAG 2024-03-31T15:06:23.513262+0000 test_transport_communicator-17123 INFO Identity of peer 1 is 34C79PQC0CWT0RPVVP3SA30MCGM7ZTA2KH35QSZ380SBEWFSXKVG * Starting test... 2024-03-31T15:06:23.516098+0000 transport-testing2-17123 INFO started NAT 2024-03-31T15:06:23.516437+0000 transport-testing2-17123 INFO started resolver service 2024-03-31T15:06:23.516801+0000 transport-testing2-17123 INFO started Peerstore 2024-03-31T15:06:23.517225+0000 transport-testing2-17123 INFO started Statistics 2024-03-31T15:06:23.517655+0000 transport-testing2-17123 INFO started communicator 2024-03-31T15:06:23.519999+0000 transport-testing2-17123 INFO started NAT 2024-03-31T15:06:23.520321+0000 transport-testing2-17123 INFO started resolver service 2024-03-31T15:06:23.520612+0000 transport-testing2-17123 INFO started Peerstore 2024-03-31T15:06:23.520918+0000 transport-testing2-17123 INFO started Statistics 2024-03-31T15:06:23.521238+0000 transport-testing2-17123 INFO started communicator 2024-03-31T15:06:23.526316+0000 util-disk-17138 WARNING `open' failed on file `/etc/resolv.conf' at disk.c:1291 with error: No such file or directory 2024-03-31T15:06:23.526362+0000 resolver-17138 ERROR Could not open /etc/resolv.conf. DNS resolution will not be possible. 2024-03-31T15:06:23.526381+0000 resolver-17138 ERROR No DNS server available. DNS resolution will not be possible. 2024-03-31T15:06:23.535897+0000 test_transport_communicator-17123 INFO Communicator available. (cc: 1, prefix: tcp) 2024-03-31T15:06:23.541310+0000 util-disk-17143 WARNING `open' failed on file `/etc/resolv.conf' at disk.c:1291 with error: No such file or directory 2024-03-31T15:06:23.541353+0000 resolver-17143 ERROR Could not open /etc/resolv.conf. DNS resolution will not be possible. 2024-03-31T15:06:23.541372+0000 resolver-17143 ERROR No DNS server available. DNS resolution will not be possible. 2024-03-31T15:06:23.551455+0000 test_transport_communicator-17123 INFO Communicator available. (cc: 1, prefix: tcp) * Short size packet test for peer 0 done. * 5000/5000 packets in 1917840 us (325 KiB/s) -- avg latency: 122 us * Short size packet test for peer 1 done. * 5000/5000 packets in 1919476 us (325 KiB/s) -- avg latency: 112 us 2024-03-31T15:06:25.545767+0000 nat-17137 WARNING upnpc failed to create port mapping 2024-03-31T15:06:25.556778+0000 nat-17142 WARNING upnpc failed to create port mapping * Long size packet test for peer 1 done. * 5000/5000 packets in 8074775 us (18 MiB/s) -- avg latency: 1682 us * Long size packet test for peer 0 done. * 5000/5000 packets in 8076921 us (18 MiB/s) -- avg latency: 1614 us 2024-03-31T15:06:37.652214+0000 test_transport_communicator-17123 ERROR Latency too high. Test failed. (Phase: 3. Sent: 2731, Received: 2731) FAIL test_communicator_bidirect-tcp (exit status: 2) Perhaps the test should rather automatically be skipped when DNS resolution is detected as not available. | ||||
| Steps To Reproduce | guix build gnunet with gnunet 0.21.0. | ||||
| Tags | No tags attached. | ||||
|
|
I updated gnunet to 0.21.1 and could not immediately reproduce the issue. I'll build it a few times to know for sure. |
|
|
Given the news entry for 0.21.1 reads "Communicator and connectivity bugfixes" I trusted that this problem is resolved. |
|
|
Nevermind, I could now reproduce the failure, using 0.21.1: FAIL: test_communicator_bidirect-tcp ==================================== 2024-03-31T16:57:32.688779+0000 test_transport_communicator-17704 INFO Identity of peer 0 is Q0Q9JZ7XM9RGG60AF6PAZY31JNN5SJG65AFCW3ZD72AFSR09976G 2024-03-31T16:57:32.690625+0000 test_transport_communicator-17704 INFO Identity of peer 1 is H8C3XYCCXA53VG3TF7BA1MJT619XYBB9BNFSG0D12ZJZPW70C260 * Starting test... 2024-03-31T16:57:32.692948+0000 transport-testing2-17704 INFO started NAT 2024-03-31T16:57:32.693237+0000 transport-testing2-17704 INFO started resolver service 2024-03-31T16:57:32.693533+0000 transport-testing2-17704 INFO started Peerstore 2024-03-31T16:57:32.693868+0000 transport-testing2-17704 INFO started Statistics 2024-03-31T16:57:32.694347+0000 transport-testing2-17704 INFO started communicator 2024-03-31T16:57:32.697163+0000 transport-testing2-17704 INFO started NAT 2024-03-31T16:57:32.697529+0000 transport-testing2-17704 INFO started resolver service 2024-03-31T16:57:32.697910+0000 transport-testing2-17704 INFO started Peerstore 2024-03-31T16:57:32.698290+0000 transport-testing2-17704 INFO started Statistics 2024-03-31T16:57:32.698770+0000 transport-testing2-17704 INFO started communicator 2024-03-31T16:57:32.706606+0000 util-disk-17719 WARNING `open' failed on file `/etc/resolv.conf' at disk.c:1291 with error: No such file or directory 2024-03-31T16:57:32.706664+0000 resolver-17719 ERROR Could not open /etc/resolv.conf. DNS resolution will not be possible. 2024-03-31T16:57:32.706689+0000 resolver-17719 ERROR No DNS server available. DNS resolution will not be possible. 2024-03-31T16:57:32.719070+0000 util-disk-17724 WARNING `open' failed on file `/etc/resolv.conf' at disk.c:1291 with error: No such file or directory 2024-03-31T16:57:32.719118+0000 resolver-17724 ERROR Could not open /etc/resolv.conf. DNS resolution will not be possible. 2024-03-31T16:57:32.719138+0000 resolver-17724 ERROR No DNS server available. DNS resolution will not be possible. 2024-03-31T16:57:32.723775+0000 test_transport_communicator-17704 INFO Communicator available. (cc: 1, prefix: tcp) 2024-03-31T16:57:32.723915+0000 test_transport_communicator-17704 INFO Communicator available. (cc: 1, prefix: tcp) * Short size packet test for peer 0 done. * 5000/5000 packets in 1503069 us (415 KiB/s) -- avg latency: 91 us * Short size packet test for peer 1 done. * 5000/5000 packets in 1566562 us (398 KiB/s) -- avg latency: 112 us 2024-03-31T16:57:34.729423+0000 nat-17718 WARNING upnpc failed to create port mapping 2024-03-31T16:57:34.729994+0000 nat-17723 WARNING upnpc failed to create port mapping * Long size packet test for peer 1 done. * 5000/5000 packets in 8435265 us (18 MiB/s) -- avg latency: 1161 us * Long size packet test for peer 0 done. * 5000/5000 packets in 8498641 us (17 MiB/s) -- avg latency: 1569 us * Size packet test for peer 0 done. * 6400/6400 packets -- avg latency: 3192127 us 2024-03-31T16:57:53.972795+0000 test_transport_communicator-17704 ERROR Latency too high. Test failed. (Phase: 3. Sent: 6400, Received: 6400) FAIL test_communicator_bidirect-tcp (exit status: 2) --- ./src/service/util/test-suite.log --------------------------------------- ==================================================== gnunet 0.21.1: src/service/util/test-suite.log ==================================================== # TOTAL: 1 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 error: in phase 'check': uncaught exception: %exception #<&invoke-error program: "make" arguments: ("check") exit-status: 2 term-signal: #f stop-signal: #f> phase `check' failed after 233.5 seconds command "make" "check" failed with status 2 builder for `/gnu/store/v8m4nxiym4p6bw6xmc3p4xchp4vimd4v-gnunet-0.21.1.drv' failed with exit code 1 |
|
|
The problem here is not the DNS error, but the test takes to long to finish. You can try modifying TIMEOUT_MULTIPLIER to 10 and see if that helps. |
|
|
Hi, I patched the TIMEOUT_MULTIPLIER to 10 but that led to building of `/gnu/store/av1nfkpq3h92pmibai55id245bd65k8a-gnunet-0.21.1.drv' timed out after 3600 seconds of silence, that is, the Guix daemon stopped the build after 1 hour of the build process not producing any output. It looks like one of the communicator tests deadlocked or otherwise hung up. |
