forked from mirrors/gecko-dev
e40b810077
This helps accumulate RDP packets related to resources being available/updated/destroyed and emit less and larger RDP packets instead or more and smaller. This appears to reduce the overhead of DevTools transport and JSWindowActor layers. The issue in browser_markup_events_toggle.js is interesting. It highlights that a resource notified before a call to WatcherActor.watchResources, may be emitted during the call to watchResources. This makes ignoreExistingResources flag a bit brittle as that resource should be considered as an existing/past one. We should probably flush past resource and probably introduce a more explicit way of handling "existing" resources on the server side. The fix in document-events.js relates to failures in browser_net_offline_mode.js. This test was passing thanks to late dom-complete event emitted on the previous WindowGlobal. Surprisingly, when reloading the page in offline mode, the previous, already existing WindowGlobal triggered the WebProgressListener and we were emitting dom-complete event. Because of throttling, this resource is no longer transfered to the client as the related target actor is already destroyed on reload. But at the end, the issue was the missing dom-interactive and dom-complete events for the error page. Regarding browser_net_ws-sse-persist-columns.js, it looks like this test was properly waiting for the WebSocket table to update. We were really lucky it was working without frequent intermittent! Similarly to the client side, DOCUMENT_EVENT's will-navigate is special and has to be emitted synchronously in order to prevent clearing things out of order. This is also true for NETWORK_EVENT_STACKTRACE which is expected to be received *before* related NETWORK_EVENT. NETWORK_EVENT_STACKTRACE is fired from the content process while NETWORK_EVENT is fired from the parent process. For now, it is easier to synchronously emit those resources rather than trying to do cross process coordination. We may revisit this choice once we start doing throttling from the parent process and may be once D143409 lands. About browser_resources_clear_resources.js, it is surprising it wasn't already failing. Differential Revision: https://phabricator.services.mozilla.com/D197772 |
||
|---|---|---|
| .. | ||
| awsy | ||
| condprofile | ||
| config | ||
| crashtest | ||
| docs | ||
| extensions | ||
| firefox-ui | ||
| geckodriver | ||
| gtest | ||
| jsshell | ||
| marionette | ||
| mochitest | ||
| modules | ||
| mozbase | ||
| mozharness | ||
| perfdocs | ||
| performance | ||
| profiles | ||
| raptor | ||
| runtimes | ||
| specialpowers | ||
| talos | ||
| test | ||
| tools | ||
| tps | ||
| web-platform | ||
| webcompat | ||
| webdriver | ||
| xpcshell | ||
| addtest.py | ||
| cppunittest.toml | ||
| mach_commands.py | ||
| moz.build | ||
| parse_build_tests_ccov.py | ||
| README.txt | ||
| remotecppunittests.py | ||
| runcppunittests.py | ||
| skipfails.py | ||
| testinfo.py | ||
| testsuite-targets.mk | ||
Common testing tools for mozilla codebase projects, test suite definitions for automated test runs, tests that don't fit anywhere else, and other fun stuff