Tuesday, May 04, 2021

Re: Update to redis-6.2.3

> *** [err]: client tracking don't cause eviction feedback loop in tests/unit/maxmemory.tcl
> Expected '0' to be between to '200' and '300' (context: type eval line 48 cmd {assert_range [r dbsize] 200 300} proc ::test)

All tests pass for me on amd64 (multiple runs) and on sparc64. As
mentioned on ICB, this failure could be a ulimit issue related to
not using PORTS_PRIVSEP.

Given the security impact, it would probably be a good idea to backport
this to -stable. The diff to 6.2.1 is relatively small and looks sane to
me.

ok tb

No comments:

Post a Comment