Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Testing a change
15 views
Skip to first unread message
Sanchit Arora
Feb 5, 2020, 4:58:59 AM2/5/20
to
How can I verify that the changes I made work (or atleast build) properly before submitting the patch?
Do I need to do ./mach build everytime? Is there a faster way?
Thanks in advance.
Do I need to do ./mach build everytime? Is there a faster way?
Thanks in advance.
Botond Ballo
Feb 5, 2020, 8:20:38 AM2/5/20
to Sanchit Arora, Mozilla Product Builds
Hi Sanchit,
On Wed, Feb 5, 2020 at 5:00 AM Sanchit Arora
<sanchit.a...@gmail.com> wrote:
> How can I verify that the changes I made work (or atleast build) properly before submitting the patch?
> Do I need to do ./mach build everytime? Is there a faster way?
Yes, you should do a `mach build` (and then, depending on the change,
either test your changes locally, or use `mach try` to run some of our
automated tests with your change applied.)
Note, only the first `mach build` after pulling from upstream should
take a long time. A subsequent `mach build` with your changes applied
will be an incremental build, which is usually much faster (e.g. a
couple of minutes).
Hope that helps,
Botond
On Wed, Feb 5, 2020 at 5:00 AM Sanchit Arora
<sanchit.a...@gmail.com> wrote:
> How can I verify that the changes I made work (or atleast build) properly before submitting the patch?
> Do I need to do ./mach build everytime? Is there a faster way?
either test your changes locally, or use `mach try` to run some of our
automated tests with your change applied.)
Note, only the first `mach build` after pulling from upstream should
take a long time. A subsequent `mach build` with your changes applied
will be an incremental build, which is usually much faster (e.g. a
couple of minutes).
Hope that helps,
Botond
0 new messages