Tag: #TAF
-
MariaDB Foundation: Reproducing and Validating MDEV‑37992 with TAF
Thanks to Mark Callaghan for filing MDEV‑37992. This regression only appears under specific LRU and buffer‑pool conditions, and requires a memory‑resident workload to expose.
Using TAF, I reproduced the issue across 11.8, 12.3, and 13.1 using both parent commits and patched commits from MDEV‑33966. The fix restores expected throughput in all branches.
The workload used was POINTS‑COVERED‑PK with 10M rows × 8 tables, 40 threads, warmup enabled, and a 90G buffer pool. TAF’s warmup iteration, rest detection, and stable‑state perf […]
-
MariaDB Foundation: Auto‑Generated User Properties in TAF 4.0 — The Piece for Ensuring Full Test Reproduction
TAF’s reproducibility story just gained its most important upgrade: every test case now produces a fully resolved, auto‑generated user properties file.
This file captures exactly what the run used — not what the user intended, not what was passed in, but the final, authoritative configuration TAF executed. It removes ambiguity, eliminates hidden dependencies, and makes every test case a fully self‑describing artifact.
This feature builds directly on the work introduced in the previous blog, where TAF gained support for embedding […]