testing/valkey-7.2.5-r0.log: test failure (segfault)
valkey fails to build on riscv64 due to a test failure (segfault when starting the server)
Relevant log output
*** [err]: Can't start the Redis server
CONFIGURATION:always-show-logo yes
notify-keyspace-events KEA
daemonize no
pidfile /var/run/redis.pid
port 21624
timeout 0
bind 127.0.0.1
loglevel verbose
logfile ''
databases 16
latency-monitor-threshold 1
repl-diskless-sync-delay 0
save ''
rdbcompression yes
dbfilename dump.rdb
dir ./tests/tmp/server.26352.27
slave-serve-stale-data yes
appendonly no
appendfsync everysec
no-appendfsync-on-rewrite no
activerehashing yes
enable-protected-configs yes
enable-debug-command yes
enable-module-command yes
propagation-error-behavior panic
shutdown-on-sigterm force
unixsocket /home/buildozer/aports/testing/valkey/src/valkey-7.2.5/tests/tmp/server.26352.27/socket
maxclients 10
ERROR:No PID detected in log ./tests/tmp/server.26352.27/stdout
*** [err]: Can't start the Redis server
CONFIGURATION:always-show-logo yes
notify-keyspace-events KEA
daemonize no
pidfile /var/run/redis.pid
port 21624
timeout 0
bind 127.0.0.1
loglevel verbose
logfile ''
databases 16
latency-monitor-threshold 1
repl-diskless-sync-delay 0
save ''
rdbcompression yes
dbfilename dump.rdb
dir ./tests/tmp/server.26352.27
slave-serve-stale-data yes
appendonly no
appendfsync everysec
no-appendfsync-on-rewrite no
activerehashing yes
enable-protected-configs yes
enable-debug-command yes
enable-module-command yes
propagation-error-behavior panic
shutdown-on-sigterm force
unixsocket /home/buildozer/aports/testing/valkey/src/valkey-7.2.5/tests/tmp/server.26352.27/socket
maxclients 10
ERROR:### Starting server for test
36234:C 25 Apr 2024 15:05:24.101 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
36234:C 25 Apr 2024 15:05:24.101 * oO0OoO0OoO0Oo Valkey is starting oO0OoO0OoO0Oo
36234:C 25 Apr 2024 15:05:24.101 * Valkey version=7.2.5, bits=64, commit=00000000, modified=0, pid=36234, just started
36234:C 25 Apr 2024 15:05:24.101 * Configuration loaded
36234:M 25 Apr 2024 15:05:24.103 * monotonic clock: POSIX clock_gettime
=== REDIS BUG REPORT START: Cut & paste starting from here ===
36234:M 25 Apr 2024 15:05:24.103 # ------------------------------------------------
36234:M 25 Apr 2024 15:05:24.103 # !!! Software Failure. Press left mouse button to continue
36234:M 25 Apr 2024 15:05:24.103 # Guru Meditation: Error registering the readable event for the module pipe. #server.c:2720
------ INFO OUTPUT ------
36234:M 25 Apr 2024 15:05:24.104 # valkey 7.2.5 crashed by signal: 11, si_code: 1
36234:M 25 Apr 2024 15:05:24.104 # Accessing address: 0x20
------ INFO OUTPUT ------
Cleanup: may take some time... OK
make[1]: *** [Makefile:494: test] Error 1
Log file: https://build.alpinelinux.org/buildlogs//build-edge-riscv64/testing/valkey/valkey-7.2.5-r0.log