Skip to content

Conversation

@ink-splatters
Copy link

Fix occasionally failing errors test by checking error patterns instead of
exact messages.

The errors test asserted exact error messages and count, but concurrent
processing causes the error detection to fire in different orders depending on
thread scheduling.

Resolves #364

…ad of

exact messages.

The errors test asserted exact error messages and count, but concurrent
processing causes the error detection to fire in different orders depending on
thread scheduling.

Changed the test to verify error detection works by checking for expected
error patterns:
- Skipped frame index detection
- Duplicate frame index detection
- Non-monotonic pts detection

This maintains test coverage while being resilient to thread scheduling
variations.

Signed-off-by: Peter A. <ink.splatters@pm.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

errors test occasionally fails due to thread scheduling effects

1 participant