From 9ac12d5aa0adcc809f4b3c8dfacf58ff79300dad Mon Sep 17 00:00:00 2001 From: Pieter Viljoen Date: Mon, 9 Nov 2026 12:48:34 -0800 Subject: [PATCH] Refer to the Log Checks Without Counting Them Co-Authored-By: Claude Opus 5.5 --- RegressionTests/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RegressionTests/README.md b/RegressionTests/README.md index 89b79250..4f864145 100644 --- a/RegressionTests/README.md +++ b/RegressionTests/README.md @@ -65,7 +65,7 @@ python3 check_results.py --baseline /Results_process.json --results : Version:` lines at the start of its `PlexCleaner_process.log`. A log lacking the version of any tool PlexCleaner checks at startup records no tool versions. It warns of each input other than the image and the plugins that differs, or that either run does not record. A plugin difference is only noted, since the plugins run after `Results_process.json` is written. So a corpus refresh, a thread-count change, a settings change, or a tool update shows beside the outcome differences it can explain. It then prints one line per file whose result, new name, `Modified` flag, `State` flags, failed operation, or invalid reason differs. -The comparison then reads the two runs' `PlexCleaner_process.log` files, for two further checks: +The comparison then reads the two runs' `PlexCleaner_process.log` files, for the further checks below: - **Output tracks.** PlexCleaner logs a file's MkvMerge track list at `Debug` each time it reads the file, so the last dump describes the output. The comparison prints one line per file whose output track types, formats, or codecs differ. PlexCleaner logs the video, audio, and subtitle tracks in that order, each in file order, so a reorder within a track type differs. A file one run dumped and the other did not differs too, even where the one dump holds no tracks. A run with no log, or whose log holds no `Debug` dump, leaves the track check unverified. That fails the comparison rather than reading as a match. - **Normalized log lines.** A parallel run interleaves files differently each time, so the two logs compare as multisets of lines. Each line first loses the fields that differ between two runs of one build. Those are the timestamps, thread and process ids, the version path segment, and the regenerated track `Uid` values. They also include ASLR addresses, the version banner lines, progress percentages, elapsed and processing times, HandBrake clock stamps, and FFmpeg progress figures. The comparison warns of each normalized line one run holds more often than the other.