Archive
2026
- jvq Shrinks Its Flaky Test History 80 Times and Lets You Pin Tests In or Out of Quarantine
- jvq Flaky Now Takes Three Lines of YAML and Shows the Tests a Crash Skipped
- jvq Replays 26 of Its Own CI Runs and Blocks a Windows Test Bug Four Pushes in a Row
- jvq Quarantines Flaky Tests So They Stop Blocking Merges
- How to Set Up jvq Flaky With GitHub Actions and Retries in pytest and Go
- jvqq Runs jq Filters on Every Core and Is Tested Against jq Byte for Byte
- jvqq Reads a Week of Gzipped Logs Faster Than zcat Can Unzip Them
- jvq Now Reads criterion, Google Benchmark, pytest-benchmark and vitest as They Are, and Gates File Sizes
- jvq Now Gates GitLab Merge Requests, With a Ready Template and a JUnit Report
- jvq Now Gates Benchmarks in Any Language, by Timing a Command or Reading a Few Lines of JSON
- jvq Flags an Update Check That Made a Go Command-Line Tool Nearly Four Times Bigger
- jvq Catches a Python Cleanup That Made URL Parsing Nearly Five Times Slower
- jvq Blocks a Go Logging Change That Added Two Allocations to Every Request
- jvq 0.6 Counts Instructions Under Valgrind to Catch a 2 Percent Slowdown on a Noisy Runner
- jvq 0.5 Keeps a History to Catch the Slowdown That Arrives One Small Merge at a Time
- How jvqq Traced a 12-Minute Payments Outage Through 3 Million Log Lines
- How jvq Holds Up Beside a Noisy Neighbour, on a Drifting Machine and With Python Scripts
- A Crashed Writer Left Three Broken Lines in a 1 GiB Log and jq Stopped at the First
- Why the Benchmark Gate Is Called jvq for Just Very Quickly
- Performance Budgets in CI Only Work When Base and Head Run Side by Side
- How jvq Was Tested With Hundreds of Runs Where the Right Answer Was Known
- First jvq Release Fails Pull Requests That Make Go Benchmarks Slower Than Their Budget