-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Description
I've seen the following repeatedly today only against CI servers, on the main branch (mentioning to rule out any V3/V2 stuff):
[xUnit.net 00:00:20.13] ConfigTests.GetInfo (RESP3) [FAIL]
Error: Expected CPU, got miscellaneous
txt=# CPU
used_cpu_sys=1.937500
used_cpu_user=0.859375
used_cpu_sys_children=0.015625
used_cpu_user_children=0.000000
used_cpu_sys_main_thread=1.937500
used_cpu_user_main_thread=0.859375
This is interesting because a RESP3 verbatim string would be:
={count}\r\n{kind}:{payload}\r\n, where kind is always exactly 3 characters, for example =16\r\ntxt:blahblahblah\r\n.
The server should not be issuing txt=... it should be txt:... - so... either the server has started responding differently, or we're borking something on the inbound.
Relevant CI is using Redis version=8.6.1, in particular in the Windows Server 2022 build.
CI starts this server in WSL with:
https://github.com/StackExchange/StackExchange.Redis/actions/runs/22959665638/workflow#L67-L75
run: |
apt-get update
apt-get install curl gpg lsb-release libgomp1 jq -y
curl -fsSL https://packages.redis.io/gpg | gpg --dearmor -o /usr/share/keyrings/redis-archive-keyring.gpg
chmod 644 /usr/share/keyrings/redis-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/redis-archive-keyring.gpg] https://packages.redis.io/deb $(lsb_release -cs) main" | tee /etc/apt/sources.list.d/redis.list
apt-get update
apt-get install -y redis
mkdir redisI'm not sure there's anything to do on this right now other than keep an eye on it.