e82fa3d957
tools/parity_hosts.json's new `known_flaky` lists the harnesses that still flake for a cause not fixed yet, each with its reason: dedicated_server (its Java client's 1.5 s step timer), remote_fireball (wall-clock sampling) and world_reopen. One of them that fails runs once more from scratch, and a pass then counts. Every retry prints a RETRIED line at the end of the run and in the CI job's summary, so a harness that passes only on its retry stays visible on PR parity and parity-main alike. The existing fresh rerun of a failure that reused oracle results is reported the same way. A known flaky harness skips that rerun and keeps reusing oracle results, because flaking doesn't mean its cached oracle runs were wrong. Repeated runs (--repeat, --flake-check) are never retried. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>