Closed Bug 1391756 Opened 2 years ago Closed 10 months ago
_readable Streams .html | Test timed out .
Bug 1391756 - Try to fix rare timeout in dom/tests/mochitest/fetch/test_readableStreams.html. r?baku
47 bytes, text/x-phabricator-request
|Details | Review|
24 failures in the last 4.5 days: https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1391756 android and windows 10 are the primary failure patterns, I think the increase is android. :gbrown, sorry to keep adding things to your list- this seems to fall into a pattern like many of the other android failures- is this something you could add to your general list of android failures and maybe a root cause will be obvious?
Whiteboard: [stockwell needswork]
I don't see an obvious connection to other current Android issues. This is a new-ish test added in bug 1128959. :bkelly/:baku -- Can you have a look / see if you can make this test more reliable?
By the way, https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=android%20mochitest-35&tochange=2d61e13b6032faa42a9f11e84b8e7a23daae842c&fromchange=3942e9db3da304e63113ab3695a4d3348b375412 suggests this started failing on Android with bug 1382377 (or perhaps the previous servo merge?).
I'll defer to baku here.
Jet, here's another potentially-related-to-Stylo intermittent failure.
(In reply to Andrew Overholt [:overholt] from comment #12) > Jet, here's another potentially-related-to-Stylo intermittent failure. (In reply to Geoff Brown [:gbrown] from comment #7) > By the way, > https://treeherder.mozilla.org/#/jobs?repo=autoland&filter- > searchStr=android%20mochitest- > 35&tochange=2d61e13b6032faa42a9f11e84b8e7a23daae842c&fromchange=3942e9db3da30 > 4e63113ab3695a4d3348b375412 suggests this started failing on Android with > bug 1382377 (or perhaps the previous servo merge?). Stylo is not yet enabled for Android.
No longer blocks: stylo-intermittent-test-failures
This very rare timeout should not block streams from shipping.
No longer blocks: streams-ship
Also removes an infinite regress of nested iframes. The original problem was that tests would start running before the child iframe was done loading. The straightforward fix is to have the child frame start the test. But this caused further error messages because the child iframe is loaded more than once; removing the iframe from the iframe fixes this.
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/7180b12513ad Try to fix rare timeout in dom/tests/mochitest/fetch/test_readableStreams.html. r=baku
10 months ago
Assignee: nobody → jorendorff
You need to log in before you can comment on or make changes to this bug.