Confirmed users
1,759
edits
ReleaseEngineering/TryChooser: Difference between revisions
ReleaseEngineering/TryChooser (view source)
Revision as of 16:09, 7 September 2017
, 7 September 2017→Examples: De-emphasize '-p all -u all' and encourage use of alternatives.
(→What if I want to run a sub-set of tests for a job?: Add warning that tag builds are broken) |
m (→Examples: De-emphasize '-p all -u all' and encourage use of alternatives.) |
||
| Line 14: | Line 14: | ||
==Examples== | ==Examples== | ||
; <tt>try: -b do -u crashtest</tt> | ; <tt>try: -b do -u crashtest</tt> | ||
: Debug and optimized builds, all available platforms, only crashtests, no talos: | : Debug and optimized builds, all available platforms, only crashtests, no talos: | ||
| Line 22: | Line 19: | ||
; <tt>try: -b d -p linux -u none</tt> | ; <tt>try: -b d -p linux -u none</tt> | ||
: Linux debug build, no unittests, no talos: | : Linux debug build, no unittests, no talos: | ||
; <tt>try: -b do -p all -u all -t none</tt> | |||
: Run all platforms, all tests, no talos. This is a lot of tests, which will use a lot of resources! Unless absolutely necessary, narrow the list of platforms and/or the list of unit tests to those you really need.: | |||
; <tt>try: -b do -u all -t chrome,nochrome</tt> | ; <tt>try: -b do -u all -t chrome,nochrome</tt> | ||