Fix murmur32 on large strings#1748
Conversation
Signed-off-by: secwall <secwall@yandex-team.ru>
de46538 to
07aa76c
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## unstable #1748 +/- ##
============================================
- Coverage 71.09% 71.02% -0.08%
============================================
Files 123 123
Lines 65531 65531
============================================
- Hits 46590 46542 -48
- Misses 18941 18989 +48 |
This will probably be taken to RC2 |
good point. let me take it with the team and we will consider adding this |
|
BTW @secwall - I run: but it did not fail. does it fail for you? |
Yes, on 64 bit Intel Ice Lake ubuntu 24.04 with current unstable and ASAN I get this: |
|
On the other side: test passes without error on unstable on my laptop (MacOS with M1). |
Current murmur32 implementation fails on large strings.
Way to reproduce crash:
```
eval 'local s = string.rep("a", 1024 * 1024 * 1024) return #cjson.encode(s..s..s)' 0
```
(Basically this is a copy-paste from large test in
`tests/unit/scripting.tcl`).
Shouldn't we run tests with `--large-memory` on daily CI so we could
find this earlier?
I think we need to backport this to 8.1 branch.
Signed-off-by: secwall <secwall@yandex-team.ru>
Current murmur32 implementation fails on large strings.
Way to reproduce crash:
```
eval 'local s = string.rep("a", 1024 * 1024 * 1024) return #cjson.encode(s..s..s)' 0
```
(Basically this is a copy-paste from large test in
`tests/unit/scripting.tcl`).
Shouldn't we run tests with `--large-memory` on daily CI so we could
find this earlier?
I think we need to backport this to 8.1 branch.
Signed-off-by: secwall <secwall@yandex-team.ru>
Current murmur32 implementation fails on large strings.
Way to reproduce crash:
```
eval 'local s = string.rep("a", 1024 * 1024 * 1024) return #cjson.encode(s..s..s)' 0
```
(Basically this is a copy-paste from large test in
`tests/unit/scripting.tcl`).
Shouldn't we run tests with `--large-memory` on daily CI so we could
find this earlier?
I think we need to backport this to 8.1 branch.
Signed-off-by: secwall <secwall@yandex-team.ru>
Current murmur32 implementation fails on large strings.
Way to reproduce crash:
```
eval 'local s = string.rep("a", 1024 * 1024 * 1024) return #cjson.encode(s..s..s)' 0
```
(Basically this is a copy-paste from large test in
`tests/unit/scripting.tcl`).
Shouldn't we run tests with `--large-memory` on daily CI so we could
find this earlier?
I think we need to backport this to 8.1 branch.
Signed-off-by: secwall <secwall@yandex-team.ru>
Current murmur32 implementation fails on large strings.
Way to reproduce crash:
(Basically this is a copy-paste from large test in
tests/unit/scripting.tcl).Shouldn't we run tests with
--large-memoryon daily CI so we could find this earlier?I think we need to backport this to 8.1 branch.