Skip running the unit tests?

[Jack Bates]

Is there a way to rebuild everything (e.g. the layout tests) without
actually running all of the unit tests every time?
I'm accustomed to rebuilding Chromium with "ninja -C out/Default" but
the slowest part of frequent rebuilds seems to be running the unit tests
-- at least I see messages like the following displayed for several
seconds at a time:

[2/163] STAMP obj/ui/base/ui_base_unittests_run.stamp

[Peter Beverloo]

You're not running the unit tests per that command, you're building them.

You can specify which target you wish to build as part of the `ninja` command. If you just want the browser, you'd use:

    $ ninja -Cout/Default chrome

Which gives you the "chrome" binary, but not any of the peripheral targets. (Use "chrome_public_apk" when building for Android.)

Thanks,

Peter

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:    http://groups.google.com/a/chromium.org/group/chromium-dev
--- You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.

[Peter Beverloo]

.. oh, and layout tests would be content shell, but we recommend using the "blink_tests" target instead :)

Peter

[Sylvain Defresne]

This does not correspond to running the unittests but to linking them. If you only are interested in building Chromium, then "ninja -C out/Default chrome" is probably the command you are interested (for desktop, the target may be different on Android).

-- Sylvain

[Marc-Antoine Ruel]

... and to clarify other comments, if you had actually ran all the tests, it would have taken a day or two, or more, depending on your workstation spec. :)

M-A