From 3c29060e87d5da23edc4dafeef725c81fe43a5d4 Mon Sep 17 00:00:00 2001 From: James Date: Thu, 14 May 2026 23:43:12 +0000 Subject: [PATCH] docs(producer): note Chromium/zlib byte-drift as known failure mode for png-sequence fixture MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Address @vanceingalls review on #847: the maxFrameFailures=0 byte-identity threshold will fail when Chromium's CDP screenshot bytes or libpng's deflate output shifts on a Docker image bump. Pin the recovery procedure in the fixture's description so a future on-call sees 'regenerate baselines' rather than spending time investigating a non-regression. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- packages/producer/tests/distributed/png-sequence/meta.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/producer/tests/distributed/png-sequence/meta.json b/packages/producer/tests/distributed/png-sequence/meta.json index d52b9f66d..6d3e78faa 100644 --- a/packages/producer/tests/distributed/png-sequence/meta.json +++ b/packages/producer/tests/distributed/png-sequence/meta.json @@ -1,6 +1,6 @@ { "name": "Distributed: png-sequence", - "description": "60-frame composition (2s @ 30fps) with transparent background, text, and a rotating SVG icon. Output is a directory of zero-padded RGBA PNGs; the assemble path merges chunk frame directories rather than concat-copying mp4 files. renderConfig.chunkSize=15 produces N=4 chunks, exercising the per-frame state continuity across chunk seams that distinguishes the assemble path's directory-merge from mp4's concat-copy.", + "description": "60-frame composition (2s @ 30fps) with transparent background, text, and a rotating SVG icon. Output is a directory of zero-padded RGBA PNGs; the assemble path merges chunk frame directories rather than concat-copying mp4 files. renderConfig.chunkSize=15 produces N=4 chunks, exercising the per-frame state continuity across chunk seams that distinguishes the assemble path's directory-merge from mp4's concat-copy. maxFrameFailures=0 makes this a strict byte-identity gate; the upstream byte sources are Chrome's CDP screenshot output and libpng's deflate, so a Chromium or zlib bump in Dockerfile.test will produce identical pixels but different bytes — the failure mode on a Chrome version bump is 'regenerate baselines via docker:test:update', not 'investigate regression'.", "tags": ["distributed", "png-sequence", "alpha"], "minPsnr": 30,