On a related note, I've neglected to document or promote a new try
syntax feature: you can filter test builders with square bracket
syntax. You could infer details from bug 802937, but in practice
probably the only useful strings are variants of:
Windows XP only - try: -b do -p win32 -u all[5.1] -t none
Single Windows platform - try: -b do -p win32 -u all[6.1] -t none
Avoid redundant OSX tests - try: -b do -p macosx64 -u all[10.7] -t none
Hopefully I got those right. Note that these restrictions apply only to
the test builders, not the build builders, so eg -p macosx64 -u
mochitests[10.6] will build on OSX 10.7 (the only place we currently
build on) and run the tests on OSX 10.6. You'll get rows on tbpl for
both 10.6 and 10.7. The 10.7 row will have a 'B', while the 10.6 row
will only have M(1 2 3 4...).
The syntax allows fancier combinations like |-u
mochitests[10.6,10.7,-Lion]| ("run if the builder name contains 10.6 or
10.7 but not if it contains Lion"), which are unlikely to be useful.
Although come to think of it, you could test on all platforms except
the "extra" OSX ones with something like |try: -b do -p all -u
all[-10.6,-10.7]|.
None of the 3 try syntax builders[1][2][3] I know of handle this
natively yet, though mine[1] allows you to press 'e' to manually edit
the try syntax before pushing. (And [3] doesn't need it.) Also, both
my[1] and the original[2] trychooser hg extensions accept a -m argument
for manually specifying the try syntax to push with. (Tip: both
mechanisms are also handy for labeling your try pushes so you can
figure out wtf you were testing when you look back at your results on
tbpl after a day or three. Example: |reimplement SSL in Befunge, try:
-b d -p linux64 -u xpcshell|.)
[1] https://bitbucket.org/sfink/trychooser
[2] https://github.com/pbiggar/trychooser
[3] http://trychooser.pub.build.mozilla.org/
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
