124
edits
No edit summary |
No edit summary |
||
Line 54: | Line 54: | ||
After that there are multiple ways to push to try; but the two most common are: | After that there are multiple ways to push to try; but the two most common are: | ||
=== Fuzzy === | ==== Fuzzy ==== | ||
Fuzzy is the currently supported and encouraged method for pushing to try. | Fuzzy is the currently supported and encouraged method for pushing to try. | ||
Line 85: | Line 85: | ||
* 'dom testing/web-platform/tests/dom' (positional arguments) are a way to specify that only tests in these directories should be run. | * 'dom testing/web-platform/tests/dom' (positional arguments) are a way to specify that only tests in these directories should be run. | ||
=== Adding stuff to a Try Run, or re-running jobs === | === Viewing your try run === | ||
After you submit your try run, it will give you a link that looks like https://treeherder.mozilla.org/#/jobs?repo=try&revision=2827e91340e5b62da31628d8f27546e3a7d53d82 (this link may not work after this job ages out of try; but https://treeherder.mozilla.org will show | |||
==== Adding stuff to a Try Run, or re-running jobs ==== | |||
If you have an existing try run that you want to add jobs to (for example additional build jobs, or to re-run tests) this can be done from the treeherder web interface without needing to send in a new try job. | If you have an existing try run that you want to add jobs to (for example additional build jobs, or to re-run tests) this can be done from the treeherder web interface without needing to send in a new try job. | ||
Line 94: | Line 98: | ||
The only caveat to this method is that it can be easy to add tests that are not typically run in a normal try run and may currently be failing in general - independent of your patchset. So keep that in mind if you get unexpected failures. | The only caveat to this method is that it can be easy to add tests that are not typically run in a normal try run and may currently be failing in general - independent of your patchset. So keep that in mind if you get unexpected failures. | ||
== Frequently Asked Questions == | |||
=== How do I modify the compiler used to build Firefox? === | |||
There's two answers to this question. | |||
**Locally**: (to be answered) | |||
**In Try**: (to be answered) | |||
=== How do I add logging to my code to figure out what is going on? === | |||
(to be answered) |
edits