View Issue Details

IDProjectCategoryView StatusLast Update
0007784GNUnetbuild processpublic2024-04-04 09:19
Reporterapteryx Assigned Toschanzen  
PrioritynormalSeverityminorReproducibilitysometimes
Status closedResolutionno change required 
Product Version0.19.3 
Summary0007784: test_core_api test failure
DescriptionHello,

The test_core_api test appears to fail in a non-deterministic fashion, as discovered with the Guix CI: https://ci.guix.gnu.org/build/686540/log/raw:


FAIL: test_core_api
===================

2023-03-31T08:21:13.130478+0000 arm-27735 WARNING Unable to bind listening socket for service `setu' to address `/tmp/guix-build-gnunet-0.19.3.drv-0/gnunet-system-runtime//gnunet-service-setu.sock': Address already in use
2023-03-31T08:21:13.130597+0000 arm-27735 WARNING Unable to bind listening socket for service `seti' to address `/tmp/guix-build-gnunet-0.19.3.drv-0/gnunet-system-runtime//gnunet-service-seti.sock': Address already in use
2023-03-31T08:21:13.130741+0000 arm-27735 WARNING Unable to bind listening socket for service `reclaim' to address `/tmp/guix-build-gnunet-0.19.3.drv-0/gnunet-user-runtime//gnunet-service-reclaim.sock': Address already in use
2023-03-31T08:21:13.130967+0000 arm-27735 WARNING Unable to bind listening socket for service `nat' to address `/tmp/guix-build-gnunet-0.19.3.drv-0/gnunet-system-runtime//gnunet-service-nat.sock': Address already in use
2023-03-31T08:21:13.131048+0000 arm-27735 WARNING Unable to bind listening socket for service `nat-auto' to address `/tmp/guix-build-gnunet-0.19.3.drv-0/gnunet-system-runtime//gnunet-service-nat-auto.sock': Address already in use
2023-03-31T08:21:13.131159+0000 arm-27735 WARNING Unable to bind listening socket for service `messenger' to address `/tmp/guix-build-gnunet-0.19.3.drv-0/gnunet-user-runtime//gnunet-service-messenger.sock': Address already in use
2023-03-31T08:26:13.222246+0000 test-core-api-27720 ERROR Assertion failed at test_core_api.c:140.
FAIL test_core_api (exit status: 42)

Steps To ReproduceI'm not sure how to reproduce it, but given its non-determinism probably running the test on a high-load environment and repeatedly may trigger it.
Additional InformationAttached is the complete build log, gzip-compressed.
TagsNo tags attached.
Attached Files
gnunet-build.log.gz (72,416 bytes)

Activities

apteryx

2024-04-01 00:47

reporter   ~0022078

This test doesn't seem to exist anymore in 0.21.1; this issue can be closed.

Issue History

Date Modified Username Field Change
2023-03-31 17:29 apteryx New Issue
2023-03-31 17:29 apteryx File Added: gnunet-build.log.gz
2024-04-01 00:47 apteryx Note Added: 0022078
2024-04-04 09:19 schanzen Assigned To => schanzen
2024-04-04 09:19 schanzen Status new => closed
2024-04-04 09:19 schanzen Resolution open => no change required