And possibly even webNavigation. It looks this got messed up during the android tab refactoring, so Kris wants to take a look. As an aside, can we maybe get our own test designation (is this "suite") for all WE tests in one place? As things currently stand, hunting down the results of WE tests in mochitest logs 1 through 10 (which also varies between platforms) is a awful dev experience.
Assignee: nobody → kmaglione+bmo
Summary: webRequest tests are not running on CI → It looks like webRequest tests are not running on CI
This is my fault. The webNavigation and webRequest tests take too long to run on the Android ARM emulator, and hit the application runtime limit if they're run with other tests. Putting them in their own subsuite fixes the problem, but also prevents them from running in any of the normal groups on try. Maybe they should be moved to their own manifest instead. (In reply to Tomislav Jovanovic :zombie from comment #0) > As an aside, can we maybe get our own test designation (is this "suite") for > all WE tests in one place? As things currently stand, hunting down the > results of WE tests in mochitest logs 1 through 10 (which also varies > between platforms) is a awful dev experience. We can consider it, but it's a separate bug.
https://hg.mozilla.org/integration/mozilla-inbound/rev/11a578cf0754b42fdd3235570ccccb986a03b333 Bug 1336757: Re-enable webnavigation and webrequest tests on infra. r=me
https://hg.mozilla.org/integration/mozilla-inbound/rev/f24dc887296771ed1d36f96caaed0e326c6f3d25 Bug 1336757: Follow-up: Disable fromCache checks, for now.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox54: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
You need to log in before you can comment on or make changes to this bug.