CastUtils TimeRanges test sometimes times out #1215
Labels
priority: P4
Nice to have / wishful thinking
status: archived
Archived and locked; will not be updated
status: unable to reproduce
Issue could not be reproduced by the team
type: code health
A code health issue
type: enhancement
New feature or request
Comments
shaka-bot
pushed a commit
that referenced
this issue
Mar 28, 2018
This test has been flakey on OSX for quite a while, but it was very occasional, and the likely cause of the flake is unrelated to the test itself, so it was never really dealt with. Recently, though, the test has been failing repeatedly on the BuildBot. This change quarantines the test so that the BuildBot will stop failing. Issue #1215 Change-Id: I1a721976c277cfb9324b0b3f9cf8eae49b17d1ca
|
@joeyparrish I'm not sure we add it, since we want to do #4214 in the future |
|
Agreed. Also this hasn't been an issue in recent momentary. |
joeyparrish
added
the
status: will not implement
joeyparrish
added
status: unable to reproduce
github-actions
bot
added
the
status: archived
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
CastUtils TimeRanges deserialize into equivalent objectssometimes times out when I run the full test suite. I've seen this happen a lot while testing other things, but annoyingly I am having a very hard time reproducing it on purpose. I ran theCastUtilstests 10k times in a row and eventually it was reproduced; notably, once it started happening (~5k runs in) it suddenly started happening multiple times in a row, which suggests it involves some kind of external state.That particular test does not have any asynchronous parts, but the beforeEach and afterEach attached to it do. In particular, the beforeEach involves loading file assets and appending a buffer to media source engine, so it might be some file I/O problem.
The text was updated successfully, but these errors were encountered: