Vlad Lazar 8cce27bedb pageserver: add a randomized read path test (#11519) ...

## Problem

Every time we make changes to the read path to fix a bug or add a
feature,
we end up adding another incomprehensible test.

## Summary of changes

Add some generic infrastructure for generating a layer map from a type
spec
and use that for a read path test. The test is randomized but uses a
fixed seed
by default. A fuzzing mode is available for confidence building.

See [Notion
page](https://www.notion.so/neondatabase/Read-Path-Unit-Testing-Fuzzing-1d1f189e0047806c8e5cd37781b0a350?pvs=4)
for a diagram of the layer map
used.

Just for fun I tried removing [this
commit](https://github.com/neondatabase/neon/pull/11494/commits/9990199cb4f26a4ab2e64372bd1301f734ddcef5)
from https://github.com/neondatabase/neon/pull/11494
and it caught the bug in the normal mode (no fuzzing required).

2025-04-14 15:31:32 +00:00

..

benches

refactor: plumb gate and cancellation down to to blob_io::BlobWriter (#11543)

2025-04-14 11:51:01 +00:00

client

feat(storcon): passthrough mark invisible and add tests (#11401)

2025-04-02 17:11:49 +00:00

compaction

utils: explicit OTEL export config and OTEL enablement via common entry point (#11139)

2025-03-12 11:07:49 +00:00

ctl

fix(pagectl/benches): scope context with debug tools (#11285)

2025-03-17 21:27:27 +00:00

pagebench

storcon: reuse reqwest http client (#11327)

2025-03-21 11:48:22 +00:00

src

pageserver: add a randomized read path test (#11519)

2025-04-14 15:31:32 +00:00

test_data

pageserver: add layer visibility calculation (#8511)

2024-08-01 09:25:35 +00:00

Cargo.toml

pageserver: add a randomized read path test (#11519)

2025-04-14 15:31:32 +00:00