tobbee / dashcheck

83%

main: 83%

LAST BUILD ON BRANCH web/error-examples

branch: web/error-examples

CHANGE BRANCH

x

Reset

Sync Branches

• web/error-examples
• changelog-mentions
• chore/deps-govulncheck
• ci/windows
• content-protection
• dashif-checks-ssr
• docs/credit-gopher
• docs/dash-6th-edition-final
• fix-elst-cut
• fix/live-no-segments-period-edges
• fix/livesim2-false-positives
• fix/test-vector-false-positives
• fix/tfdt-optional
• main
• release/v0.3.0
• release/v0.3.1
• serve-port-check
• update-xsd-dash-mpd
• web-progress-history
• web/examples

Build # 40643098209

Build Type

Pull #20

github

Committed by tobbee

Commit Message

fix: report CLOCK-LOCAL only for a local clock far off

CLOCK-LOCAL (info) was reported for every check with a reference clock,
also when this computer's clock was a few milliseconds off, so nearly
every live stream had one info. The checks use the synchronized clock,
so the local clock does not change any result, and the clock line of the
report already gives its offset.

CLOCK-LOCAL is now reported only when the local clock is further off the
reference clock than CLOCK-SKEW allows a UTCTiming source: 500ms plus
half the round trip and half the resolution of the measurement.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EagxH7tnicDrEzrQXfrmg7

Pull Request Pull Request #20: web: error examples from test vectors, green for no errors, quieter CLOCK-LOCAL

Coverage Stats

5 of 5 new or added lines in 1 file covered. (100.0%)

1 existing line in 1 file now uncovered.

5434 of 6584 relevant lines covered (82.53%)

0.83 hits per line