Summary
Can't start server: Bad directive or wrong number of arguments in tests/unit/dummy-startup.tcl is failing in CI.
Failing test(s)
- Test name:
[no test]
- Test file:
tests/unit/dummy-startup.tcl
- CI link(s):
Error stack trace
Can't start /home/runner/work/valkey/valkey/src/valkey-server
CONFIGURATION:
always-show-logo yes
notify-keyspace-events KEA
daemonize no
pidfile /var/run/valkey.pid
port 23777
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.15581.1
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
enable-debug-assert yes
hide-user-data-from-log no
unixsocket /home/runner/work/valkey/valkey/tests/tmp/server.15581.1/socket
invalid-config-key-that-does-not-exist bogus
ERROR:
*** FATAL CONFIG FILE ERROR (Version 255.255.255) ***
Reading the configuration file, at line 30
>>> 'invalid-config-key-that-does-not-exist bogus'
Bad directive or wrong number of arguments
Environments: test-ubuntu-jemalloc
Auto-created by Test Failure Detector
Summary
Can't start server: Bad directive or wrong number of argumentsintests/unit/dummy-startup.tclis failing in CI.Failing test(s)
[no test]tests/unit/dummy-startup.tcltest-ubuntu-jemalloc: CI linkError stack trace
Environments:
test-ubuntu-jemallocAuto-created by Test Failure Detector