83
edits
Changes
Added section on debugging desktop product failures.
* browsers: Android: Fennec 64.0.2, GeckoView Example, Fenix, and Reference Browser
* measuring: Power consumption for idle Android browsers, with about:blank loaded and app backgrounded, over a 10-minute duration
== Debugging Desktop Product Failures ==
As of now, there is no easy way to do this. Raptor was not built for debugging functional failures. Hitting these in Raptor is indicative that we lack functional test coverage so regression tests should be added for those failures after they are fixed.
To debug a functional failure in Raptor you can follow these steps:
# If bug 1653617 has not landed yet, apply the patch.
# Add the --verbose flag to the extra-options list [https://searchfox.org/mozilla-central/source/taskcluster/ci/test/raptor.yml#98-101 here].
# If the --setenv doesn't exist yet ([https://bugzilla.mozilla.org/show_bug.cgi?id=1494669 bug 1494669]), then add your MOZ_LOG environment variables to give you additional logging [https://searchfox.org/mozilla-central/source/testing/raptor/raptor/webextension/desktop.py#42 here].
# If the flag does exist, then you can add the MOZ_LOG variables to the [https://searchfox.org/mozilla-central/source/taskcluster/ci/test/raptor.yml raptor.yml] configuration file.
# Push to try if you can't reproduce the failure locally.
You can follow [https://bugzilla.mozilla.org/show_bug.cgi?id=1655554 bug 1655554] as we work on improving this workflow.
== Debugging the Raptor Web Extension ==
