83
edits
TestEngineering/Performance/Raptor: Difference between revisions
→Debugging Desktop Product Failures
| Line 616: | Line 616: | ||
You can follow [https://bugzilla.mozilla.org/show_bug.cgi?id=1655554 bug 1655554] as we work on improving this workflow. | You can follow [https://bugzilla.mozilla.org/show_bug.cgi?id=1655554 bug 1655554] as we work on improving this workflow. | ||
In some cases, you might not be able to get logging for what you are debugging. In this case, you should make your own debug prints with printf or something along those lines ([https://matrix.to/#/!LfXZSWEroPFPMQcYmw:mozilla.org/$r_azj7OipkgDzQ75SCns2QIayp4260PIMHLWLApJJNg?via=mozilla.org&via=matrix.org&via=rduce.org see :agi's debugging work for an example]). | In some cases, you might not be able to get logging for what you are debugging (browser console logging for instance). In this case, you should make your own debug prints with printf or something along those lines ([https://matrix.to/#/!LfXZSWEroPFPMQcYmw:mozilla.org/$r_azj7OipkgDzQ75SCns2QIayp4260PIMHLWLApJJNg?via=mozilla.org&via=matrix.org&via=rduce.org see :agi's debugging work for an example]). | ||
== Debugging the Raptor Web Extension == | == Debugging the Raptor Web Extension == | ||