Add test that exercises "too large removal buffer" code
All checks were successful
Tests / 64 bit versions total: 8099, passed: 8099
Tests / Debug total: 8097, passed: 8097
Tests / SIMD fallback total: 8099, passed: 8099
Tests / Release [clang] total: 8099, passed: 8099
Clang |Total|New|Outstanding|Fixed|Trend |:-:|:-:|:-:|:-:|:-: |0|0|0|0|:clap:
Tests / gcc total: 8099, passed: 8099
GNU C Compiler (gcc) |Total|New|Outstanding|Fixed|Trend |:-:|:-:|:-:|:-:|:-: |0|0|0|0|:clap:
Tests / Release [clang,aarch64] total: 5366, passed: 5366
Tests / Coverage total: 5416, passed: 5416
Code Coverage #### Project Overview No changes detected, that affect the code coverage. * Line Coverage: 97.61% (3182/3260) * Branch Coverage: 42.26% (19285/45639) * Complexity Density: 0.00 * Lines of Code: 3260 #### Quality Gates Summary Output truncated.
weaselab/conflict-set/pipeline/head This commit looks good

This commit is contained in:
2024-11-14 16:40:47 -08:00
parent 08958d4109
commit f403c78410

View File

@@ -1,3 +1,4 @@
import struct
from conflict_set import *
@@ -164,6 +165,16 @@ def test_fixup_256():
cs.check(read(0, bytes([1]), bytes([2])))
def test_large_removal_buffer():
with DebugConflictSet() as cs:
for i in range(1000):
# create extra gc work
for j in range(100):
cs.addWrites(1000 + i)
cs.addWrites(1000 + i, write(struct.pack(">l", i) + bytes([0] * 100000)))
cs.setOldestVersion(i)
if __name__ == "__main__":
# budget "pytest" for ctest integration without pulling in a dependency. You can of course still use pytest in local development.
import argparse